Method and device for transmitting and receiving wireless signal in wireless communication system

ABSTRACT

The present invention relates to a wireless communication system and particularly to a method and a device therefor, the method comprising the steps of: detecting an SSB, the SSB comprising 15 kHz-granularity-based offset information; determining, on the basis of the 15 kHz-granularity-based offset information, a subcarrier offset used to identify the frequency position of a CORESET linked to the SSB; and monitoring, on the basis of the subcarrier offset, the CORESET linked to the SSB.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/711,571, filed on Apr. 1, 2022, which is a continuation ofInternational Application No. PCT/KR2020/013519, filed on Oct. 5, 2020,which claims the benefit of U.S. Provisional Application No. 63/012,029,filed on Apr. 17, 2020, and Korean Application Nos. 10-2020-0028488,filed on Mar. 6, 2020, 10-2020-0026307, filed on Mar. 3, 2020,10-2019-0142507, filed on Nov. 8, 2019, 10-2019-0141806, filed on Nov.7, 2019, and 10-2019-0122676, filed on Oct. 2, 2019. The disclosures ofthe prior applications are incorporated by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates to a wireless communication system, andmore particularly, to a method and apparatus for transmitting andreceiving a wireless signal.

BACKGROUND

Wireless communication systems have been widely deployed to providevarious types of communication services such as voice or data. Ingeneral, a wireless communication system is a multiple access systemthat supports communication of multiple users by sharing availablesystem resources (a bandwidth, transmission power, etc.). Examples ofmultiple access systems include a code division multiple access (CDMA)system, a frequency division multiple access (FDMA) system, a timedivision multiple access (TDMA) system, an orthogonal frequency divisionmultiple access (OFDMA) system, and a single carrier frequency divisionmultiple access (SC-FDMA) system.

SUMMARY

An aspect of the present disclosure is to provide a method and apparatusfor efficiently transmitting and receiving a wireless signal.

It will be appreciated by persons skilled in the art that the objectsthat could be achieved with the present disclosure are not limited towhat has been particularly described hereinabove and the above and otherobjects that the present disclosure could achieve will be more clearlyunderstood from the following detailed description.

In an aspect of the present disclosure, a method performed by a userequipment (UE) in a wireless communication system is provided. Themethod may include: detecting a synchronization signal block (SSB),wherein the SSB may include 15 kHz-granularity-based offset information;determining a subcarrier offset used to identify a frequency location ofa control resource set (CORESET) related to the SSB based on the 15kHz-granularity-based offset information; and monitoring the CORESETrelated to the SSB based on the subcarrier offset. Based on detection ofthe SSB in an unlicensed band, (1) a difference between asynchronization raster in the unlicensed band and a center frequency ofthe SSB may be limited to a multiple of 30 kHz, and (2) the subcarrieroffset may indicate only a multiple of 30 kHz based on the 15kHz-granularity-based offset information.

In another aspect of the present disclosure, a UE for use in a wirelesscommunication system is provided. The UE may include: at least oneprocessor; and at least one computer memory operably connected to the atleast one processor and configured to, when executed, cause the at leastone processor to perform operations. The operations may include:detecting an SSB, wherein the SSB may include 15 kHz-granularity-basedoffset information; determining a subcarrier offset used to identify afrequency location of a CORESET related to the SSB based on the 15kHz-granularity-based offset information; and monitoring the CORESETrelated to the SSB based on the subcarrier offset. Based on detection ofthe SSB in an unlicensed band, (1) a difference between asynchronization raster in the unlicensed band and a center frequency ofthe SSB may be limited to a multiple of 30 kHz, and (2) the subcarrieroffset may indicate only a multiple of 30 kHz based on the 15kHz-granularity-based offset information.

In still another aspect of the present disclosure, an apparatus for a UEis provided. The apparatus may include: at least one processor; and atleast one computer memory operably connected to the at least oneprocessor and configured to, when executed, cause the at least oneprocessor to perform operations. The operations may include: detectingan SSB, wherein the SSB may include 15 kHz-granularity-based offsetinformation; determining a subcarrier offset used to identify afrequency location of a CORESET related to the SSB based on the 15kHz-granularity-based offset information; and monitoring the CORESETrelated to the SSB based on the subcarrier offset. Based on detection ofthe SSB in an unlicensed band, (1) a difference between asynchronization raster in the unlicensed band and a center frequency ofthe SSB may be limited to a multiple of 30 kHz, and (2) the subcarrieroffset may indicatee only a multiple of 30 kHz based on the 15kHz-granularity-based offset information.

In a further aspect of the present disclosure, a computer-readablestorage medium having at least one computer program that, when executed,cause at least one processor to perform operations. The operations mayinclude: detecting an SSB, wherein the SSB may include 15kHz-granularity-based offset information; determining a subcarrieroffset used to identify a frequency location of a CORESET related to theSSB based on the 15 kHz-granularity-based offset information; andmonitoring the CORESET related to the SSB based on the subcarrieroffset. Based on detection of the SSB in an unlicensed band, (1) adifference between a synchronization raster in the unlicensed band and acenter frequency of the SSB may be limited to a multiple of 30 kHz, and(2) the subcarrier offset may indicate only a multiple of 30 kHz basedon the 15 kHz-granularity-based offset information.

Preferably, based on the detection of the SSB in the unlicensed band,the subcarrier offset may indicate a multiple of 15 kHz.

Preferably, the 15 kHz-granularity-based offset information may include4 bits of ssb-SubcarrierOffset as least significant bits (LSBs).

Preferably, based on the detection of the SSB in the unlicensed band,the subcarrier offset may be determined to be equal to a value obtainedby setting one LSB of the 15 kHz-granularity-based offset information to‘0’.

Preferably, based on the detection of the SSB in the unlicensed band,the one LSB of the 15 kHz-granularity-based offset information may beused to identify SSB candidates in a quasi-co-location (QCL)relationship.

According to the present disclosure, a wireless signal may betransmitted and received efficiently in a wireless communication system.

It will be appreciated by persons skilled in the art that the effectsthat can be achieved with the present disclosure are not limited to whathas been particularly described hereinabove and other advantages of thepresent disclosure will be more clearly understood from the followingdetailed description taken in conjunction with the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the disclosure and are incorporated in and constitute apart of this application, illustrate embodiments of the disclosure andtogether with the description serve to explain the principle of thedisclosure. In the drawings:

FIG. 1 illustrates physical channels used in a 3rd generationpartnership project (3GPP) system as an exemplary wireless communicationsystem and a general signal transmission method using the same;

FIG. 2 illustrates a radio frame structure;

FIG. 3 illustrates a resource grid of a slot;

FIG. 4 illustrates mapping of physical channels in a slot.

FIGS. 5A and 5B illustrate a wireless communication system supporting anunlicensed band;

FIG. 6 illustrates a method of occupying resources in an unlicensedband;

FIGS. 7 to 9 illustrate synchronization signal block (SSB)structures/transmission;

FIG. 10 illustrates a system information acquisition process;

FIG. 11 illustrates the locations of an SSB and a control resource set(CORESET);

FIGS. 12 to 19 illustrate configurations of am SSB/CORESET according toproposals of the present disclosure;

FIGS. 20 to 22 illustrate signal transmission and reception according toproposals of the present disclosure; and

FIGS. 23 to 26 illustrate a communication system 1 and wireless devices,which are applied to the present disclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure are applicable to a variety ofwireless access technologies such as code division multiple access(CDMA), frequency division multiple access (FDMA), time divisionmultiple access (TDMA), orthogonal frequency division multiple access(OFDMA), and single carrier frequency division multiple access(SC-FDMA). CDMA can be implemented as a radio technology such asUniversal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can beimplemented as a radio technology such as Global System for Mobilecommunications (GSM)/General Packet Radio Service (GPRS)/Enhanced DataRates for GSM Evolution (EDGE). OFDMA can be implemented as a radiotechnology such as Institute of Electrical and Electronics Engineers(IEEE) 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Worldwideinteroperability for Microwave Access (WiMAX)), IEEE 802.20, and EvolvedUTRA (E-UTRA). UTRA is a part of Universal Mobile TelecommunicationsSystem (UMTS). 3rd Generation Partnership Project (3GPP) Long TermEvolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA, andLTE-Advanced (A) is an evolved version of 3GPP LTE. 3GPP NR (New Radioor New Radio Access Technology) is an evolved version of 3GPP LTE/LTE-A.

As more and more communication devices require a larger communicationcapacity, there is a need for mobile broadband communication enhancedover conventional radio access technology (RAT). In addition, massivemachine type communications (MTC) capable of providing a variety ofservices anywhere and anytime by connecting multiple devices and objectsis another important issue to be considered for next generationcommunications. Communication system design considering services/UEssensitive to reliability and latency is also under discussion. As such,introduction of new radio access technology considering enhanced mobilebroadband communication (eMBB), massive MTC, and ultra-reliable and lowlatency communication (URLLC) is being discussed. In the presentdisclosure, for simplicity, this technology will be referred to as NR(New Radio or New RAT).

For the sake of clarity, 3GPP NR is mainly described, but the technicalidea of the present disclosure is not limited thereto.

In a wireless communication system, a user equipment (UE) receivesinformation through downlink (DL) from a base station (BS) and transmitinformation to the BS through uplink (UL). The information transmittedand received by the BS and the UE includes data and various controlinformation and includes various physical channels according totype/usage of the information transmitted and received by the UE and theBS.

FIG. 1 illustrates physical channels used in a 3GPP NR system and ageneral signal transmission method using the same.

When powered on or when a UE initially enters a cell, the UE performsinitial cell search involving synchronization with a BS in step S101.For initial cell search, the UE receives synchronization signal block(SSB). The SSB includes a primary synchronization signal (PSS), asecondary synchronization signal (SSS), and a physical broadcast channel(PBCH). The UE synchronizes with the BS and acquires information such asa cell Identifier (ID) based on the PSS/SSS. Then the UE may receivebroadcast information from the cell on the PBCH. In the meantime, the UEmay check a downlink channel status by receiving a downlink referencesignal (DL RS) during initial cell search.

After initial cell search, the UE may acquire more specific systeminformation by receiving a physical downlink control channel (PDCCH) andreceiving a physical downlink shared channel (PDSCH) based oninformation of the PDCCH in step S102.

The UE may perform a random access procedure to access the BS in stepsS103 to S106. For random access, the UE may transmit a preamble to theBS on a physical random access channel (PRACH) (S103) and receive aresponse message for preamble on a PDCCH and a PDSCH corresponding tothe PDCCH (S104). In the case of contention-based random access, the UEmay perform a contention resolution procedure by further transmittingthe PRACH (S105) and receiving a PDCCH and a PDSCH corresponding to thePDCCH (S106).

After the foregoing procedure, the UE may receive a PDCCH/PDSCH (S107)and transmit a physical uplink shared channel (PUSCH)/physical uplinkcontrol channel (PUCCH) (S108), as a general downlink/uplink signaltransmission procedure. Control information transmitted from the UE tothe BS is referred to as uplink control information (UCI). The UCIincludes hybrid automatic repeat and requestacknowledgement/negative-acknowledgement (HARQ-ACK/NACK), schedulingrequest (SR), channel state information (CSI), etc. The CSI includes achannel quality indicator (CQI), a precoding matrix indicator (PMI), arank indicator (RI), etc. While the UCI is transmitted on a PUCCH ingeneral, the UCI may be transmitted on a PUSCH when control informationand traffic data need to be simultaneously transmitted. In addition, theUCI may be aperiodically transmitted through a PUSCH according torequest/command of a network.

FIG. 2 illustrates a radio frame structure. In NR, uplink and downlinktransmissions are configured with frames. Each radio frame has a lengthof 10 ms and is divided into two 5-ms half-frames (HF). Each half-frameis divided into five 1-ms subframes (SFs). A subframe is divided intoone or more slots, and the number of slots in a subframe depends onsubcarrier spacing (SCS). Each slot includes 12 or 14 orthogonalfrequency division multiplexing (OFDM) symbols according to a cyclicprefix (CP). When a normal CP is used, each slot includes 14 OFDMsymbols. When an extended CP is used, each slot includes 12 OFDMsymbols.

Table 1 exemplarily shows that the number of symbols per slot, thenumber of slots per frame, and the number of slots per subframe varyaccording to the SCS when the normal CP is used.

TABLE 1 SCS (15 * 2{circumflex over ( )}u) N^(slot) _(symb) N^(frame,u)_(slot) N^(subframe,u) _(slot)  15 KHz (u = 0) 14  10  1  30 KHz (u = 1)14  20  2  60 KHz (u = 2) 14  40  4 120 KHz (u = 3) 14  80  8 240 KHz (u= 4) 14 160 16 *N^(slot) _(symb): Number of symbols in a slot*N^(frame,u) _(slot): Number of slots in a frame *N^(subframe,u)_(slot): Number of slots in a subframe

Table 2 illustrates that the number of symbols per slot, the number ofslots per frame, and the number of slots per subframe vary according tothe SCS when the extended CP is used.

TABLE 2 SCS (15 * 2{circumflex over ( )}u) N^(slot) _(symb) N^(frame,u)_(slot) N^(subframe,u) _(slot) 60 KHz (u = 2) 12 40 4

The frame structure is merely an example. The number of subframes, thenumber of slots, and the number of symbols in a frame may vary.

In the NR system, different OFDM numerologies (e.g., SCSs) may beconfigured for a plurality of cells aggregated for one UE. Accordingly,the (absolute time) duration of a time resource including the samenumber of symbols (e.g., a subframe (SF), slot, or TTI) (collectivelyreferred to as a time unit (TU) for convenience) may be configured to bedifferent for the aggregated cells. A symbol may be an OFDM symbol (orCP-OFDM symbol) or an SC_FDMA symbol (or a discrete Fouriertransform-spread-OFDM (DFT-s-OFDM) symbol).

In NR, various numerologies (or SCSs) are supported to support various5G services. For example, with an SCS of 15 kHz, a wide area intraditional cellular bands is supported, while with an SCS of 30 kHz/60kHz, a dense urban area, a lower latency, and a wide carrier bandwidthare supported. With an SCS of 60 kHz or higher, a bandwidth larger than24.25 GHz is be supported to overcome phase noise.

An NR frequency band may be defined by two types of frequency ranges,FR1 and FR2. FR1 and FR2 may be configured as described in Table 3. FR2may refer to millimeter wave (mmW).

TABLE 3 Frequency Range Corresponding Subcarrier designation frequencyrange Spacing FR1  450 MHz-7125 MHz  15, 30, 60 kHz FR2 24250 MHz-52600MHz 60, 120, 240 kHz

FIG. 3 illustrates a resource grid of a slot. A slot includes aplurality of symbols in the time domain. For example, when the normal CPis used, the slot includes 14 symbols. However, when the extended CP isused, the slot includes 12 symbols. A carrier includes a plurality ofsubcarriers in the frequency domain. A resource block (RB) is defined asa plurality of consecutive subcarriers (e.g., 12 consecutivesubcarriers) in the frequency domain. A bandwidth part (BWP) may bedefined to be a plurality of consecutive physical RBs (PRBs) in thefrequency domain and correspond to a single numerology (e.g., SCS, CPlength, etc.). The carrier may include up to N (e.g., 5) BWPs. Datacommunication may be performed through an activated BWP, and only oneBWP may be activated for one UE. In the resource grid, each element isreferred to as a resource element (RE), and one complex symbol may bemapped to each RE.

FIG. 4 illustrates a structure of a slot. In the NR system, a frame hasa self-contained structure in which a DL control channel, DL or UL data,a UL control channel, and the like may all be contained in one slot. Forexample, the first N symbols (hereinafter, DL control region) in theslot may be used to transmit a DL control channel (e.g., PDCCH), and thelast M symbols (hereinafter, UL control region) in the slot may be usedto transmit a UL control channel (e.g., PUCCH). N and M are integersgreater than or equal to 0. A resource region (hereinafter, a dataregion) that is between the DL control region and the UL control regionmay be used for DL data (e.g., PDSCH) transmission or UL data (e.g.,PUSCH) transmission. The GP provides a time gap for the BS and UE totransition from the transmission mode to the reception mode or from thereception mode to the transmission mode. Some symbols at the time ofDL-to-UL switching in a subframe may be configured as the GP.

The PDCCH delivers DCI. For example, the PDCCH (i.e., DCI) may carryinformation about a transport format and resource allocation of a DLshared channel (DL-SCH), resource allocation information of an uplinkshared channel (UL-SCH), paging information on a paging channel (PCH),system information on the DL-SCH, information on resource allocation ofa higher-layer control message such as an RAR transmitted on a PDSCH, atransmit power control command, information about activation/release ofconfigured scheduling (CS), and so on. The DCI includes a cyclicredundancy check (CRC). The CRC is masked with various identifiers (IDs)(e.g. a radio network temporary identifier (RNTI)) according to an owneror usage of the PDCCH. For example, if the PDCCH is for a specific UE,the CRC is masked by a UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH isfor a paging message, the CRC is masked by a paging-RNTI (P-RNTI). Ifthe PDCCH is for system information (e.g., a system information block(SIB)), the CRC is masked by a system information RNTI (SI-RNTI). Whenthe PDCCH is for an RAR, the CRC is masked by a random access-RNTI(RA-RNTI).

The PDCCH may be transmitted in a control resource set (CORESET). TheCORESET is defined as a set of resource element groups (REGs) with agiven numerology (e.g., SCS, CP length, and so on). A plurality ofCORESETs for one UE may overlap with each other in the time/frequencydomain. The CORESET may be configured by system information (e.g.,master information block (MIB)) or by UE-specific higher layer signaling(e.g., radio resource control (RRC) signaling). Specifically, the numberof RBs and the number of symbols (up to 3 symbols) included in theCORESET may be configured by higher layer signaling.

The UE may obtain DCI transmitted over a PDCCH by decoding (blinddecoding) a set of PDCCH candidates. The set of PDCCH candidates decodedby the UE is defined as a PDCCH search space set. A search space set maybe a common search space (CSS) or a UE-specific search space (USS). TheUE may obtain DCI by monitoring PDCCH candidates in one or more searchspace sets configured by an MIB or higher layer signaling. Each CORESETconfiguration may be associated with one or more search space sets, andeach search space set may be associated with one CORESET configuration.One search space set may be determined based on the followingparameters.

controlResourceSetId: A set of control resources related to the searchspace set

monitoringSlotPeriodicityAndOffset A PDCCH monitoring periodicity (in aunit of slot) and a PDCCH monitoring offset (in a unit of slot)

monitoringSymbolsWithinSlot: A PDCCH monitoring pattern (e.g., firstsymbol(s) in the CORESET) in a PDCCH monitoring slot

nrofCandidates: The number of PDCCH candidates (one of 0, 1, 2, 3, 4, 5,6, and 8) for each AL={1, 2, 4, 8, 16}

Table 4 shows the characteristics of each search space type.

TABLE 4 Search Type Space RNTI Use Case Type0- Common SI-RNTI on aprimary cell SIB Decoding PDCCH Type0A- Common SI-RNTI on a primary cellSIB Decoding PDCCH Type1- Common RA-RNTI or TC-RNTI on a Msg2, Msg4PDCCH primary cell decoding in RACH Type2- Common P-RNTI on a primarycell Paging PDCCH Decoding Type3- Common INT-RNTI, SFI-RNTI, PDCCHTPC-PUSCH-RNTI, TPC- PUCCH-RNTI, TPC-SRS- RNTI, C-RNTI, MCS-C-RNTI, orCS-RNTI(s) UE C-RNTI, or MCS-C-RNTI, or User specific SpecificCS-RNTI(s) PDSCH decoding

Table 5 exemplarily shows DCI formats transmitted on the PDCCH.

TABLE 5 DCI format Usage 0_0 Scheduling of PUSCH in one cell 0_1Scheduling of PUSCH in one cell 1_0 Scheduling of PDSCH in one cell 1_1Scheduling of PDSCH in one cell 2_0 Notifying a group of UEs of the slotformat 2_1 Notifying a group of UEs of the PRB(s) and OFDM symbol(s)where UE may assume no transmission is intended for the UE 2_2Transmission of TPC commands for PUCCH and PUSCH 2_3 Transmission of agroup of TPC commands for SRS transmissions by one or more UEs

FIGS. 5A and 5B illustrate an exemplary wireless communication systemsupporting an unlicensed band applicable to the present disclosure. Inthe following description, a cell operating in a licensed band (L-band)is defined as an L-cell, and a carrier of the L-cell is defined as a(DL/UL) LCC. A cell operating in an unlicensed band (U-band) is definedas a U-cell, and a carrier of the U-cell is defined as a (DL/UL) UCC.The carrier/carrier-frequency of a cell may refer to the operatingfrequency (e.g., center frequency) of the cell. A cell/carrier (e.g.,CC) is commonly called a cell.

When carrier aggregation is supported, one UE may use a plurality ofaggregated cells/carriers to exchange a signal with the BS. When one UEis configured with a plurality of CCs, one CC may be set to a primary CC(PCC), and the remaining CCs may be set to secondary CCs (SCCs).Specific control information/channels (e.g., CSS PDCCH, PUCCH) may betransmitted and received only on the PCC. Data may be transmitted andreceived on the PCC/SCC. FIG. 5A shows a case in which the UE and BSexchange signals on both the LCC and UCC (non-standalone (NSA) mode). Inthis case, the LCC and UCC may be set to the PCC and SCC, respectively.When the UE is configured with a plurality of LCCs, one specific LCC maybe set to the PCC, and the remaining LCCs may be set to the SCC. FIG. 5Acorresponds to the LAA of the 3GPP LTE system. FIG. 5B shows a case inwhich the UE and BS exchange signals on one or more UCCs with no LCC(standalone (SA) mode). In this case, one of the UCCs may be set to thePCC, and the remaining UCCs may be set to the SCC. Both the NSA mode andSA mode may be supported in the U-band of the 3GPP NR system.

FIG. 6 illustrates an exemplary method of occupying resources in anunlicensed band. According to regional regulations for an unlicensedband, a communication node should determine whether other communicationnode(s) is using a channel in the unlicensed band, before signaltransmission. Specifically, the communication node may determine whetherother communication node(s) is using a channel by performing carriersensing (CS) before signal transmission. When the communication nodeconfirms that any other communication node is not transmitting a signal,this is defined as confirming clear channel assessment (CCA). In thepresence of a CCA threshold predefined by higher-layer signaling (RRCsignaling), when the communication node detects energy higher than theCCA threshold in the channel, the communication node may determine thatthe channel is busy, and otherwise, the communication node may determinethat the channel is idle. For reference, the WiFi standard (e.g.,801.11ac) specifies a CCA threshold of −62 dBm for a non-WiFi signal anda CCA threshold of −82 dBm for a WiFi signal. When determining that thechannel is idle, the communication node may start signal transmission ina UCell. The above-described series of operations may be referred to asa listen-before-talk (LBT) or channel access procedure (CAP). LBT andCAP may be interchangeably used.

In Europe, two LBT operations are defined: frame based equipment (FBE)and load based equipment (LBE). In FBE, one fixed frame is made up of achannel occupancy time (e.g., 1 to 10 ms), which is a time period duringwhich once a communication node succeeds in channel access, thecommunication node may continue transmission, and an idle periodcorresponding to at least 5% of the channel occupancy time, and CCA isdefined as an operation of observing a channel during a CCA slot (atleast 20 us) at the end of the idle period. The communication nodeperforms CCA periodically on a fixed frame basis. When the channel isunoccupied, the communication node transmits during the channeloccupancy time, whereas when the channel is occupied, the communicationnode defers the transmission and waits until a CCA slot in the nextperiod.

In LBE, the communication node may set q∈{4, 5, . . . , 32} and thenperform CCA for one CCA slot. When the channel is unoccupied in thefirst CCA slot, the communication node may secure a time period of up to(13/32)q ms and transmit data in the time period. When the channel isoccupied in the first CCA slot, the communication node randomly selectsN∈{1, 2, . . . , q}, stores the selected value as an initial value, andthen senses a channel state on a CCA slot basis. Each time the channelis unoccupied in a CCA slot, the communication node decrements thestored counter value by 1. When the counter value reaches 0, thecommunication node may secure a time period of up to (13/32)q ms andtransmit data.

Embodiments

FIG. 7 illustrates the structure of an SSB. A UE may perform cellsearch, system information acquisition, beam alignment for initialaccess, DL measurement, and so on based on an SSB. The term SSB isinterchangeably used with an SS/PBCH block. The SSB is made up of fourconsecutive OFDM symbols, each carrying a PSS, a PBCH, an SSS/PBCH, or aPBCH. Each of the PSS and the SSS includes one OFDM symbol by 127subcarriers, and the PBCH includes 3 OFDM symbols by 576 subcarriers.Polar coding and quadrature phase shift keying (QPSK) are applied to thePBCH. The PBCH includes data REs and demodulation reference signal(DMRS) REs in each OFDM symbol. There are three DMRS REs per RB, andthree data REs exist between DMRS REs.

FIG. 8 illustrates exemplary SSB transmission. Referring to FIG. 8 , anSSB is transmitted periodically according to an SSB periodicity. Adefault SSB periodicity that the UE assumes during initial cell searchis defined as 20 ms. After cell access, the SSB periodicity may be setto one of {5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms} by a network (e.g.,a BS). An SSB burst set is configured at the start of an SSB period. TheSSB burst set includes a 5-ms time window (i.e., a half-frame), and anSSB may be transmitted up to L times in the SSB burst set. The maximumtransmission number L of an SSB may be given as follows according to thefrequency band of a carrier. One slot includes up to two SSBs.

For frequency range of up to 3 GHz, L=4

For frequency range from 3 GHz to 6 GHz, L=8

For frequency range from 6 GHz to 52.6 GHz, L=64

The time positions of candidate SSBs in an SS burst set may be definedas follows according to SCSs. The time positions of candidate SSBs areindexed with (SSB indexes) 0 to L-1 in time order in the SSB burst set(i.e., half-frame). In this document, the term ‘candidate SSB’ isinterchangeably used with the term ‘SSB candidate’.

Case A (15 kHz SCS): the starting symbol index of a candidate SSB isgiven by {2, 8}+14*n.

For operation without shared spectrum channel access (e.g., licensedband (L-band), licensed cell (LCell), etc.): for a carrier frequencybelow 3 GHz, n=0 or 1. For a carrier frequency of 3 to 6 GHz, n=0, 1, 2,or 3.

For operation with shared spectrum channel access (e.g., unlicensed band(U-band), unlicensed cell (UCell), etc.): n=0, 1, 2, 3, or 4.

Case B (30 kHz SCS): the starting symbol index of a candidate SSB isgiven by {4, 8, 16, 20}+28*n. For a carrier frequency below 3 GHz, n=0.For a carrier frequency of 3 to 6 GHz, n=0 or 1.

Case C (30 kHz SCS): the starting symbol index of a candidate SSB isgiven by {2, 8}+14*n.

For operation without shared spectrum channel access: (1) assumingpaired spectrum operation, for a carrier frequency below 3 GHz, n=0 or1, and for a carrier frequency within FR1 and higher than 3 GHz, n=0, 1,2, or 3; (2) assuming unpaired spectrum operation, for a carrierfrequency below 2.4 GHz, n=0 or 1, and for a carrier frequency withinFR1 and higher than 2.4 GHz, n=0, 1, 2, or 3.

For operation with shared spectrum channel access: n=0, 1, 2, 3, 4, 6,7, 8, or 9.

Case D (120 kHz SCS): the starting symbol index of a candidate SSB isgiven by {4, 8, 16, 20}+28*n. For a carrier frequency within FR2, n=0,1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, or 18.

Case E (240 kHz SCS): the starting symbol index of a candidate SSB isgiven by {8, 12, 16, 20, 32, 36, 40, 44}+56*n. For a carrier frequencywithin FR2, n=0, 1, 2, 3, 5, 6, 7, or 8.

For operation with shared spectrum channel access, the UE may assumethat transmission of SSBs in a half frame is within a discovery bursttransmission window starting from the first symbol of the first slot inthe half frame. The UE may be provided with the duration of a discoveryburst transmission for each serving cell. If no discovery bursttransmission window duration is not provided, the UE may assume that thediscovery burst transmission window duration is a half frame. For eachserving cell, the UE may assume that the repetition periodicity of thediscovery burst transmission window is the same as to the repetitionperiodicity of a half-frame for SSB reception. The UE may assume thatamong SSBs of the serving cell, SSB(s) having the same value of(N^(PBCH) _(DM-RS) mod N^(QCL) _(SSB)) within the same discovery bursttransmission window or over different discovery burst transmissionwindows among the SSBs of the serving cell are quasi co-located (QCLed),where N^(PBCH) _(DM-RS) denotes the index of a DM-RS sequence for aPBCH, and N^(QCL) _(SSB) may be obtained as follows: (i) N^(QCL) _(SSB)may be provided by ssbPositionQCL-Relationship, or (ii) N^(QCL) _(SSB)may be obtained from an MIB in an SSB according to Table 6 ifssbPositionQCL-Relationship is not provided.

TABLE 6 LSB of subCarrierSpacingCommon ssb-SubcarrierOffset N^(QCL)_(SSB) scs15or60 0 1 scs15or60 1 2 scs30or120 0 4 scs30or120 1 8

ssbSubcarrierSpacingCommon denotes an SCS of RMSI only for the case of“operation without shared spectrum”. The UE may assume that the numberof SSBs transmitted on the serving cell within the discovery bursttransmission window is not greater than N^(QCL) _(SSB). The UE maydetermine the index of an SSB according to (N^(PBCH) _(DM-RS) modN^(QCL) _(SSB)) or (i^(˜) mod N^(QCL) _(SSB)), where i^(˜) denotes theindex of a candidate SSB. Accordingly, one or more candidate SSBs maycorrespond to one SSB index. Candidate SSBs corresponding to the sameSSB index may be QCLed.

FIG. 9 illustrates an example of SS/PBCH block candidate positions.Specifically, FIG. 9 shows a case where N^(QCL) _(SSB) is set to 4 andssb-PositionsInBurst is set to ‘10100000’. In this case, only an SSBwith SSB (=SS/PBCH block) index #0/#2 may be transmitted.ssb-PositionsInBurst and N^(QCL) _(SSB) may be used to provide a ratematching pattern within a discovery reference signal (DRS) transmissionwindow (or discovery burst transmission window). For example, the UE mayperform rate matching on all SSB candidate position indices QCLed withactually transmitted SSB indices that are provided byssb-PositionsInBurst. In FIG. 9 , the UE may perform rate matching ontime/frequency resources of an SSB candidate location index0/2/4/6/8/10/12/14/16/18. Therefore, when receiving a PDSCH scheduled bya PDCCH with a CRC scrambled by a C-RNTI, MCS-C-RNTI, CS-RNTI, RA-RNTI,MsbB-RNTI, P-RNTI, TC-RNTI, etc. or a PDSCH with SPS (or with a CRCscrambled by an SI-RNTI if a system information indicator in an PDCCH(i.e., DCI) is set to 1), the UE may assume SSB transmission accordingto ssb-PositionsInBurst if PDSCH resource allocation overlaps with PRBsincluding SSB transmission resources (e.g. SSB candidate position index0/2/4/6/8/10/12/14/16/18). That is, the UE may assume that the PRBsincluding the SSB transmission resources are not available (not mappedto) for the PDSCH in OFDM symbols where the SSB is transmitted.

FIG. 10 illustrates a system information (SI) acquisition process. Inthe NR system, when the UE attempts initial access, the UE may obtainPDCCH configuration information for receiving SI (e.g., SIB1) from aPBCH payload (or MIB) (S1102). In this case, the PDCCH configurationinformation may mean: (1) information on time/frequency resources of aCORESET (hereinafter, CORESET#0) in which a PDCCH scheduling a PDSCHcarrying SI is to be transmitted; and information about a CSS set(hereinafter, Type0-PDCCH CSS set) associated with CORESET#0.Accordingly, the UE may receive the PDCCH (scheduling the PDSCH carryingthe SI) based on the PDCCH configuration information and obtain the SIfrom the PDSCH scheduled by the corresponding PDCCH (S1104). Inaddition, the UE may send a request for on-demand SI to the BS (S1106)and receive the requested SI (S1108).

SI except for the MIB may be referred to as remaining minimum systeminformation (RMSI). The MIB includes information/parameters related toreception of SIB1 (SystemInformationBlockType1) and is transmitted overa PBCH of an SSB. Information in the MIB may include the followingfields, and details thereof may be found in 3GPP TS 38.331.

subCarrierSpacingCommon ENUMERATED {scs15or60, scs30or120},

ssb-SubcarrierOffset INTEGER (0 . . . 15),

pdcch-ConfigSIB1 INTEGER (0 . . . 255),

dmrs-TypeA-Position ENUMERATED {pos2, pos3},

Details of each field are summarized in Table 7.

TABLE 7 pdcch-ConfigSIB1 Determines a common CORESET (i.e., CORESET#0),a common search space and necessary PDCCH parameters. If the fieldssb-SubcarrierOffset indicates that SIB1 is absent, the fieldpdcch-ConfigSIB1 indicates the frequency positions where the UE may findSS/PBCH block with SIB1 or the frequency range where the network doesnot provide SS/PBCH block with SIB1. ssb-SubcarrierOffset Corresponds tok_(SSB), which is the frequency domain offset between SSB and theoverall resource block grid in number of subcarriers. This field mayindicate that this cell does not provide SIB1 and that there is hence noCORESET#0 configured in MIB. In this case, the field pdcch-ConfigSIB1may indicate the frequency positions where the UE may (not) find aSS/PBCH with a CORESET and search space for SIB1. Upon detection of aSS/PBCH block, the UE determines that a control resource set forType0-PDCCH common search space is present if k_(SSB) <= 23 for FR1(Frequency Range 1; Sub-6 GHz; 450 to 6000 MHz) and if k_(SSB) <=11 forFR2 (Frequency Range 2; mm-Wave; 24250 to 52600 MHz). k_(SSB) representsa frequency/subcarrier offset between subcarrier 0 of SS/PBCH block tosubcarrier 0 of common resource block for SSB. For FR2 only values up to11 are applicable. The UE determines that a control resource set forType0-PDCCH common search space is not present if k_(SSB) > 23 for FR1and if k_(SSB) > 11 for FR2. subCarrierSpacingCommon Subcarrier spacingfor SIB1, Msg.2/4 for initial access, paging and broadcast SI- messages.If the UE acquires this MIB on an FR1 carrier frequency, the valuescs15or60 corresponds to 15 kHz and the value scs30or120 corresponds to30 kHz. If the UE acquires this MIB on an FR2 carrier frequency, thevalue scs15or60 corresponds to 60 kHz and the value scs30or120corresponds to 120 kHz. dmrs-TypeA-Position Position of (first) DM-RSfor downlink (e.g., PDSCH) and uplink (e.g., PUSCH). pos2 represents the2^(nd) symbol in a slot and pos2 represents the 3^(rd) symbol in a slot.

FIG. 11 illustrates frequency positions of an SSB and CORESET#0. Achannel raster is defined by a subset of RF reference frequencies usedto identify an RF channel position. The RF reference frequency isdefined for all frequency bands, and the granularity (i.e. frequencyspacing) of the RF reference frequency may be, for example, 5 kHz (inthe frequency range of 0 to 3000 MHz) and 15 kHz (in the frequency rangeof 3000 to 24250 MHz). A synchronization raster is a subset of channelrasters and indicates the frequency position of an SSB used by the UE toobtain SI, SS_(REF). SS_(REF) may coincide with the center frequency of20 PRBs occupied by an SSB. Table 8 shows a relationship betweenSS_(REF) and a global synchronization channel number (GSCN).

TABLE 8 Frequency SS Block (SSB) frequency Range position SS_(REF) GSCNRange of GSCN   0-3000 N * 1200 kHz + M * 50 3N + (M − 3)/2   2-7498 MHzkHz, N = 1:2499, M ∈ {1, 3, 5} (Note 1) 3000-24250 3000 MHz + N * 1.44MHz 7499 + N 7499-22255 MHz N = 0:14756 NOTE 1: The default value foroperating bands with SCS spaced channel raster is M = 3.

After SSB detection, the UE may determine: (i) a plurality of contiguousRBs and one or more contiguous symbols included in a CORESET (e.g.,CORESET#0) and; (ii) a PDCCH occasion (i.e., time-domain location forPDCCH reception) (e.g., search space #0) based on information in the MIB(e.g., pdcch-ConfigSIB1). Specifically, pdcch-ConfigSIB1 is 8-bitinformation. In this case, (i) is determined based on the four mostsignificant bits (MSBs) (or MSB four bits) of pdcch-ConfigSIB1 (see 3GPPTS 38.213 Tables 13-1 to 13-10), and (ii) is determined based on thefour least significant bits (LSBs) (or LSB four bits) ofpdcch-ConfigSIB1 (see 3GPP TS 38.213 Tables 13-11 to 13-15).

Table 9 shows information indicated by the four MSBs ofpdcch-ConfigSIB1.

TABLE 9 SS/PBCH block Number of Number of and CORESET RBs Symbols OffsetIndex multiplexing pattern N^(CORESET) _(RB) N^(CORESET) _(symb) (RBs)*0 1 48 1 2 1 1 48 1 6 2 1 48 2 2 3 1 48 2 6 4 1 48 3 2 5 1 48 3 6 6 1 961 28 7 1 96 2 28 8 1 96 3 28 9-15 Reserved *denotes an offset betweenthe first RB of an SSB and the first RB of an RMSI CORESET.

The position of CORESET#0 in the frequency domain is determined by asubcarrier offset and an RB offset with respect to the SSB. Referring toFIG. 11 , k_(SSB) denotes a subcarrier offset from subcarrier #0 of acommon resource block (CRB), N^(SSB) _(CRB) to subcarrier #0 of the SSB.Here, N^(SSB) _(CRB) is identified by a higher layer (e.g., RRC)parameter, offsetToPointA, and k_(SSB) is a 5-bit value and consists of:MSB 1 bit of 3 bits of MIB used for candidate SSB indices (=MSB 1 bit ofk_(SSB))+4 bits of ssb-SubcarrierOffset (=LSB 4 bits of k_(SSB)). The RBoffset denotes an offset from the smallest RB index of CORESET#0 to thesmallest RB index of the CRB overlapping with the first RB of thecorresponding SSB, which may be determined based on the offset (RB) ofTable 9.

As described above, the channel raster is defined with a spacing of 15kHz in the NR system (in a band above 3 GHz) (see Table 8), and thecorresponding value is used by the UE as a reference frequency forsignal transmission and reception on a carrier. For example, the channelraster may mean the center frequency of a PRB resource region related toa corresponding carrier/BWP. NR-U may be defined in a 5 and/or 6 GHzband. In an environment where NR-U coexists with Wi-Fi (and/or LTE LAA),the resource region of a carrier/BWP bandwidth may be aligned with thatof Wi-Fi. For example, considering that Wi-Fi is defined based on 20-MHzinterval channelization such as 5150 to 5170 MHz and 5170 to 5190 MHz,the channel raster value may be defined to be at most aligned with 5150to 5170 MHz and 5170 to 5190 MHz for a NR-U carrier bandwidth of 20 MHzor at most aligned with 5150 to 5190 MHz for a NR-U carrier bandwidth of40 MHz. In addition, a specific channel raster value may be selectedfrom among channel raster values defined in NR according to thecarrier/BWP bandwidth and related frequency region to be aligned with aWi-Fi channel (hereinafter, down selection). As an example, for the 20MHz carrier bandwidth corresponding to 5150 to 5170 MHz or 5170 to 5190MHz, the channel raster value may be defined as 5160 MHz (correspondingto N_(REF)=744000 in Table 8) or 5180.01 MHz (N_(REF)=745334 in Table8). As another example, for the 40 MHz carrier bandwidth correspondingto 5150 to 5190 MHz, the channel raster value may be defined as 5169.99MHz (corresponding to N_(REF)=744666 in Table 8). In addition, in anenvironment where NR-U does not coexist with Wi-Fi (and/or LTE LAA), allchannel raster values with the 15 kHz SCS may be allowed with no downselection, or a plurality of channel raster values may be defineddepending on the carrier bandwidth and related frequency region if downselection is performed.

In NR, the synchronization raster is defined with a sparser density thanthe channel raster in consideration of UE complexity for SS/PBCH blockdetection. The synchronization raster may coincide with the centerfrequency of 20 PRBs occupied by an SS/PBCH block. Some ofsynchronization raster values with a spacing of 1.44 MHz (defined in NR)may be defined as the synchronization raster for NR-U, which may bedefined in the 5 and/or 6 GHz band. Specifically, one synchronizationraster value may be defined for each 20 MHz. The correspondingsynchronization raster value may be defined to be close to the centerfrequency of 20 MHz. Alternatively, the corresponding synchronizationraster value may be defined such that the SS/PBCH block is located atthe end of 20 MHz as much as possible. For example, in a regioncorresponding to 5150 to 5170 MHz shown in FIG. 12 , the synchronizationraster value may be defined as 5155.68 MHz (corresponding to GSCN=8996of Table 8) so that the synchronization raster value belongs to existingsynchronization raster candidates of NR and is close to 5150 MHz as muchas possible while 20 PRBs of the SS/PBCH block are included in thecorresponding region. Also, in the present disclosure, it is basicallyassumed that the RB grid of the carrier/BWP (consisting of 51 PRBs) isaligned with the RB grid of CORESET#0 (consisting of 48 PRBs) as shownin the example of FIG. 12 .

Hereinafter, the present disclosure proposes a method of configuringresources of CORESET#0 for SI acquisition in the NR system operating inan unlicensed band, and a method for a UE to analyze the resources. Forexample, the present disclosure proposes a method of configuring aresource region of CORESEST#0 based on a PBCH payload (or MIB) when asynchronization raster and a channel raster are defined. In addition,the present disclosure proposes a method of configuring a resourceregion of CORESEST#0 based on a PBCH payload (or MIB) in an SS/PBCHblock when the SS/PBCH block is transmitted at a center frequency whichdoes not corresponding to the synchronization raster.

The proposed methods of the present disclosure may be applied to onlyoperations in the NR-U system/cell (e.g., shared spectrum). For example,if the system is not the NR-U system/cell (e.g., shared spectrum), themethods proposed in the present disclosure may be combined with methodsused in the current NR system

1) Receiver (Entity A) (e.g., UE)

[Method #1] An offset value from a specific RE of an SS/PBCH block(e.g., the first RE in the minimum RB index) to a specific RE ofCORESET#0 (e.g., the first RE in the minimum RB index) may be configuredby the PBCH payload of the corresponding SS/PBCH block. In this case,the offset value may be defined at the RB and/or RE level, and the RBlevel offset value may have a range (that varies depending on eachfrequency band) determined based on the synchronization raster andchannel raster defined for NR-U frequency bands. Here, the RE refers toa unit on the frequency axis, and the order of REs may be equivalent tothe order of REs in one OFDM symbol. Accordingly, an RE may be replacedwith a subcarrier.

When the UE attempts initial access in frequency bands of the NR-Usystem, the UE may expect an SS/PBCH and CORESET#0 with an SCS of 30kHz. In this case, the frequency-domain position and time-domainduration of CORESET#0 may be defined the same as those of the current NRsystem. Table 10 shows sets of RBs and slot symbols of CORESET for aType0-PDCCH search space set when the SCS of {SS/PBCH block, PDCCH} is{30, 30} kHz for frequency bands with a minimum channel bandwidth of 5or 10 MHz in the current NR system.

TABLE 10 SS/PBCH block Number of Number of and CORESET RBs symbolsOffset Index multiplexing pattern N^(CORESET) _(RB) N^(CORESET) _(symb)(RBs) 0 1 24 2 0 1 1 24 2 1 2 1 24 2 2 3 1 24 2 3 4 1 24 2 4 5 1 24 3 06 1 24 3 1 7 1 24 3 2 8 1 24 3 3 9 1 24 3 4 10 1 48 1 12 11 1 48 1 14 121 48 1 16 13 1 48 2 12 14 1 48 2 14 15 1 48 2 16

However, the following restrictions may be imposed in NR-U: the numberof RBs of 30 kHz CORESET#0 is 48, and the time-domain duration thereofis one or two (OFDM) symbols. In addition, the range of the RB leveloffset value may be determined by the synchronization raster and channelraster defined for NR-U frequency bands. For example, for a combinationof each band for operating the NR-U system and the carrier/BWPbandwidth, if the maximum/minimum of the RB level offset value betweenthe minimum RB index of the SS/PBCH block and the minimum RB index ofCORESET#0 is in the range of [A, B], some or all of the values between Aand B in the column corresponding to the offset of Table 10 may besignaled. For example, when A=−2 and B=5, 8 states among a total of 16states correspond to one symbol, and the remaining 8 states correspondto two symbols. Each of the 8 states may signal an RB level offset valuebetween −2 to 5. Additionally, the RE level offset value may be signaledby the value of k_(SSB) in the same way as in the NR system.

Table 11 shows the configuration of CORESET#0 in the case of A=−2 andB=5.

TABLE 11 SS/PBCH block Number of Number of and CORESET RBs symbolsOffset Index multiplexing pattern N^(CORESET) _(RB) N^(CORESET) _(symb)(RBs) 0 1 48 1 −2 1 1 48 1 −1 2 1 48 1 0 3 1 48 1 1 4 1 48 1 2 5 1 48 13 6 1 48 1 4 7 1 48 1 5 8 1 48 2 −2 9 1 48 2 −1 10 1 48 2 0 11 1 48 2 112 1 48 2 2 13 1 48 2 3 14 1 48 2 4 15 1 48 2 5

As an example, as shown in FIG. 13 , when the UE receives an SS/PBCHblock with a center frequency of 5155.68 MHz, which is thesynchronization raster defined for a 5150 to 5170 MHz band, the UE mayobtain ‘offset X’, which is a frequency offset between the SS/PBCH blockand CORESET#0, from the PBCH payload of the corresponding SS/PBCH block.For example, when the UE is signaled with index #4 of Table 11 andk_(SSB)=6 through the PBCH payload, the UE may recognize that thefrequency region of CORESET#0 starts from a position apart by 2 RBs and6 REs from the SS/PBCH block.

As another example, the frequency-domain position difference betweenRB#0 of the SS/PBCH block and RB#0 of 51 PRBs may be within 1 PRB asshown in FIG. 14 , and the frequency-domain position difference betweenRB#0 of the SS/PBCH block and RB#0 of 51 PRBs may be more than 4 PRBs asshown in FIG. 15 . For FIG. 14 , it may be preferable that the first PRBof CORESET#0 is aligned with the second PRB among the 51 PRBs inconsideration of interference with adjacent 20 MHz bands. In this case,−1 PRB may be required as the RB offset. Similarly, for FIG. 15 , it maybe preferable that the last PRB of CORESET#0 is aligned with the secondlast PRB among the 51 PRBs in consideration of interference withadjacent 20 MHz bands. In this case, 2 PRBs may be required as the RBoffset. To this end, information about RB offset values from a minimumof −1 PRB to a maximum of 2 PRBs needs to be configured. The locationsof the time/frequency-domain resources of CORESET#0 may be configured bythe PBCH payload according to a method shown in Table 12 below. In Table12, “reserved” states are to prepare for when an RB offset value that isnot in the range of [−1, 2] is required. Alternatively, RB offsets inthe range of [−k, k] (e.g., k=2) and reserved states may be signaled.

In addition, when the SS/PBCH block is transmitted based on the 15 kHzSCS, the number of RBs (or PRBs) may be set to 96, and the RB offset maybe set to values corresponding to twice the RB offset values based onthe 30 kHz SCS (in Table 12) as shown in Table 13. Alternatively, asshown in Table 14, the number of RBs (or PRBs) may be set to 96, and theRB offset may be determined by an RB granularity based on the 15 kHz SCSin addition to values corresponding to twice the RB offset values basedon the 30 kHz SCS (in Table 12). Alternatively, as shown in Table 15,the RB offset may be determined by values reflecting differences betweenabsolute frequency-domain resources corresponding to 20 PRBs of theSS/PBCH block in addition to values corresponding to twice the RB offsetvalues based on the 30 kHz SCS (in Table 12). That is, since the SS/PBCHblock consists of 20 PRBs regardless of SCSs, when the SCS is 15 kHz,frequency-domain resources may decrease (by 20 PRBs) compared to whenthe SCS is 30 kHz. Therefore, the RB offset values may be filled withvalues corresponding to {double of RB offset values based on 30 kHzSCS}+10 (because 10 PRBs are reduced with respect to the centerfrequency of the SS/PBCH block) (or with RB granularity values betweenthe minimum/maximum values of the corresponding values) as shown inTable 15.

Table 12 shows the configuration of CORESET#0 when the SS/PBCH block isbased on the 30 kHz SCS, and Tables 13 to 15 show the configurations ofCORESET#0 when the SS/PBCH block is based on the 15 kHz SCS. In thetables, a to d denote integers, respectively. The RB offset is definedbased on the SCS of a CORESET (i.e., CORESET#0) for a Type0-PDCCH CSSset. As shown in FIGS. 12 to 15 , the SCS of CORESET#0 is the same asthe SCS of the corresponding SS/PBCH block.

TABLE 12 SS/PBCH block Number of Number of and CORESET RBs symbolsOffset Index multiplexing pattern N^(CORESET) _(RB) N^(CORESET) _(symb)(RBs) 0 1 48 1 −1 (=a)  1 1 48 1 0 (=b) 2 1 48 1 1 (=c) 3 1 48 1 2 (=d)4 1 48 1 Reserved 5 1 48 1 Reserved 6 1 48 1 Reserved 7 1 48 1 Reserved8 1 48 2 −1 (=a)  9 1 48 2 0 (=b) 10 1 48 2 1 (=c) 11 1 48 2 2 (=d) 12 148 2 Reserved 13 1 48 2 Reserved 14 1 48 2 Reserved 15 1 48 2 Reserved

TABLE 13 SS/PBCH block Number of Number of and CORESET RBs symbolsOffset Index multiplexing pattern N^(CORESET) _(RB) N^(CORESET) _(symb)(RBs) 0 1 96 1 −2 (=2a)  1 1 96 1 0 (=2b) 2 1 96 1 2 (=2c) 3 1 96 1 4(=2d) 4 1 96 1 Reserved 5 1 96 1 Reserved 6 1 96 1 Reserved 7 1 96 1Reserved 8 1 96 2 −2 (=2a)  9 1 96 2 0 (=2b) 10 1 96 2 2 (=2c) 11 1 96 24 (=2d) 12 1 96 2 Reserved 13 1 96 2 Reserved 14 1 96 2 Reserved 15 1 962 Reserved

TABLE 14 SS/PBCH block Number of Number of and CORESET RBs symbolsOffset Index multiplexing pattern N^(CORESET) _(RB) N^(CORESET) _(symb)(RBs) 0 1 96 1 −2 (=2a)  1 1 96 1 −1  2 1 96 1 0 (=2b) 3 1 96 1 1 4 1 961 2 (=2c) 5 1 96 1 3 6 1 96 1 4 (=2d) 7 1 96 1 Reserved 8 1 96 2 −2(=2a)  9 1 96 2 −1  10 1 96 2 0 (=2b) 11 1 96 2 1 12 1 96 2 2 (=2c) 13 196 2 3 14 1 96 2 4 (=2d) 15 1 96 2 Reserved

TABLE 15 SS/PBCH block Number of Number of and CORESET RBs symbolsOffset Index multiplexing pattern N^(CORESET) _(RB) N^(CORESET) _(symb)(RBs) 0 1 96 1  8 (=2a + 10) 1 1 96 1 10 (=2b + 10) 2 1 96 1 12 (=2c +10) 3 1 96 1 14 (=2d + 10) 4 1 96 1 Reserved 5 1 96 1 Reserved 6 1 96 1Reserved 7 1 96 1 Reserved 8 1 96 2  8 (=2a + 10) 9 1 96 2 10 (=2b + 10)10 1 96 2 12 (=2c + 10) 11 1 96 2 14 (=2d + 10) 12 1 96 2 Reserved 13 196 2 Reserved 14 1 96 2 Reserved 15 1 96 2 Reserved

[Method #2] An offset value from the channel raster corresponding to afrequency band in which an SS/PBCH block is transmitted to a specificfrequency resource (e.g., center frequency) of CORESET#0 may beconfigured by the PBCH payload of the corresponding SS/PBCH block. Inthis case, the offset value may be defined at the RB and/or RE level,and the RB level offset value may have a range (that varies depending oneach frequency band) determined based on a channel raster defined forNR-U frequency bands.

If channel raster candidates vary depending on coexistence with Wi-Fi,the channel raster in this proposal may mean a channel raster when thecoexistence with Wi-Fi is assumed. In addition, if channel rastercandidates vary according to the carrier/BWP bandwidth, the channelraster in this proposal may mean a channel raster when a specificcarrier bandwidth (e.g., 20 MHz) is assumed.

For example, for a combination of each band for NR-U operation and aspecific carrier bandwidth (e.g., 20 MHz), if the maximum/minimum of theRB level offset value from the channel raster to the specific frequencyresource (e.g., center frequency) of CORESET#0 is in the range of [A,B], some or all of the values between A and B in the columncorresponding to the offset of Table 10 may be signaled. For example,when A=−3 and B=4, 8 states among a total of 16 states correspond to onesymbol, and the remaining 8 states correspond to two symbols. Each ofthe 8 states may signal an RB level offset value between −3 to 4. Inaddition, the RE level offset value may be signaled by the value ofk_(SSB) in the same way as in the NR system.

Table 16 shows the configuration of CORESET#0 in the case of A=−3 andB=4.

TABLE 16 SS/PBCH block Number of Number of and CORESET RBs symbolsOffset Index multiplexing pattern N^(CORESET) _(RB) N^(CORESET) _(symb)(RBs) 0 1 48 1 −3 1 1 48 1 −2 2 1 48 1 −1 3 1 48 1 0 4 1 48 1 1 5 1 48 12 6 1 48 1 3 7 1 48 1 4 8 1 48 2 −3 9 1 48 2 −2 10 1 48 2 −1 11 1 48 2 012 1 48 2 1 13 1 48 2 2 14 1 48 2 3 15 1 48 2 4

As an example, as shown in FIG. 16 , when the UE receives an SS/PBCHblock with a center frequency of 5155.68 MHz, which is thesynchronization raster defined for a 5150 to 5170 MHz band, the UE mayobtain an offset value between a specific channel raster value (e.g.,5160 MHz) defined in the corresponding band and the center frequency ofCORESET#0 from the PBCH payload of the corresponding SS/PBCH block. Forexample, when the UE is signaled with index #3 of Table 16 and k_(SSB)=0through the PBCH payload, the UE may identify the frequency resourceregion of CORESET#0 consisting of 48 PRBs with the channel raster as thecenter frequency. As another example, when the offset value from thechannel raster corresponding to the frequency band in which the SS/PBCHblock is transmitted to the specific frequency resource (e.g., centerfrequency) of CORESET#0 is configured by the PBCH payload of the SS/PBCHblock, only the RE level offset value (except for the RB level offset)may be signaled as the corresponding offset value. That is, the centerfrequency of CORESET#0 may be aligned with the specific channel raster,and the RB grid of CORESET#0 may be aligned with the RB grid of thecarrier/BWP, which is managed by the BS in the corresponding frequencyband, by the k_(SSB) value. In this case, the k_(SSB) value may mean nRE offset(s) (in the lower frequency direction) with respect to thechannel raster, which is the reference point (in this case, n may be anegative number) or mean n RE offset(s) (in the higher frequencydirection) (in this case, n may be a positive number). For example, ifthe k_(SSB) value is between 1 and 12, it may mean RE offset(s) in thehigher frequency direction (for example, if k_(SSB)=n, it may mean n REoffset(s) in the higher frequency direction). If the k_(SSB) value isbetween 13 and 23, it may mean RE offset(s) in the lower frequencydirection (for example, if k_(SSB)=n, it may mean (n-12) RE offset(s) inthe lower frequency direction).

[Method #3] Candidates may be defined for a plurality of CORESET#0frequency resource regions corresponding to a band in which an SS/PBCHblock is transmitted, and which one of the candidates is actually usedmay be configured by the PBCH payload of the corresponding SS/PBCHblock. In this case, the plurality of candidates for CORESET#0 frequencyresource regions may vary depending on the carrier/BWP bandwidth, thenumber of PRBs used in the carrier/BWP bandwidth, and/or the location ofa 20 MHz band in which the SS/PBCH block is transmitted in thecarrier/BWP bandwidth (for example, whether the SS/PBCH block is locatedat a higher 20 MHz band or a lower 20 MHz band of a 40 MHz carrierbandwidth). In addition, the RB grid as well as the location ofCORESET#0 may be informed by signaling.

For convenience, when a 20 MHz carrier is configured with 51 PRBs in the5150 to 5170 MHz band as shown in FIG. 16 , the offset value between theSS/PBCH block and CORESET#0 may be defined as offset X. When a 20 MHzcarrier is configured with 50 PRBs in the 5150 to 5170 MHz band as shownin FIG. 17 , the offset value between the SS/PBCH block and CORESET#0may be defined as offset Y. When a 40 MHz carrier is configured with 106PRBs in the 5150 to 5190 MHz band as shown in FIG. 18 , the offset valuebetween the SS/PBCH block and CORESET#0 may be defined as offset Z.

The BS may inform one of offsets X/Y/Z through the PBCH payload. Whenthe UE receives the SS/PBCH block with a center frequency of 5155.68MHz, which is the synchronization raster defined in the 5150 to 5170 MHzband, the UE may obtain one of offsets X/Y/Z from the PBCH payload ofthe corresponding SS/PBCH block. The UE may identify the location of theminimum RB of CORESET#0 by applying the received offset. This examplerelates to signaling of the offset value between the SS/PBCH block andCORESET#0, but an offset value between the channel raster and a specificfrequency resource (e.g., center frequency) of CORESET#0 may also besignaled as in [Method #2]. In addition, the corresponding offset valuemay be defined/interpreted differently according to the frequency bandof the SS/PBCH block.

[Method #4] If the UE needs to decode the PBCH payload for an SS/PBCHblock other than the synchronization raster to determine the locationsof frequency resources of CORESET#0, the UE may reinterpret informationin the decoded PBCH payload by assuming that the SS/PBCH block istransmitted in the synchronization raster defined for a bandcorresponding to the corresponding SS/PBCH block.

According to the following motivation, the BS may need to provideinformation on CORESET#0 frequency resources even for the SS/PBCH blockother than the synchronization raster.

Different operators may coexist in an unlicensed band, and the sameoperator may be in unplanned deployment environments, so the same(physical) cell ID may be used between cells in the same band. Toprevent the UE from being confused by this problem, the BS may need totransmit information about CORESET#0 and a type0-PDCCH CSS set forhigher layer signaling (e.g., SIB1) containing information on anoperator ID, a public land mobile network (PLMN) ID, or a global cell ID(even for an SS/PBCH block that is not transmitted in thesynchronization raster). For example, assuming that gNB #X transmits anSS/PBCH block in frequency #X and UE #Y is associated with gNB #Y, gNB#Y may instruct UE #Y to perform measurement on frequency #X (frequency#X may not match the synchronization raster). After performing themeasurement on frequency #X, UE #Y may report a discovered cell ID ofgNB #X and the measurement result of a corresponding cell to gNB #Y. IfgNB #Y does not know whether gNB #X is the same operator, gNB #Y mayinstruct UE #Y to read higher layer signaling (e.g., SIB1) containinginformation on the operator ID, PLMN ID or global cell ID of gNB #X andreport the information on the operator ID, PLMN ID, or global cell ID.Upon receiving the corresponding information, gNB #Y may update theoperator information on gNB #X. Considering this operation, gNB #Xtransmitting the SS/PBCH block in frequency #X may need to transmitinformation about CORESET#0 and a type0-PDCCH CSS set for scheduling aPDSCH carrying higher layer signaling containing information on anoperator ID, a PLMN ID, or a global cell ID explicitly/implicitly in theSS/PBCH block (for convenience, although such higher layer signaling isnamed SIB1, it may correspond to cell-common higher layer signaling).

For example, as shown in FIG. 19 , if the UE decodes the PBCH payload ofan SS/PBCH block having, as the center frequency, frequency #X ratherthan the synchronization raster, the UE may interpret information in thedecoded PBCH payload based on an SS/PBCH block having as the centerfrequency 5155.68 MHz, which is the synchronization raster defined forthe 5150 to 5170 MHz band corresponding to the corresponding SS/PBCHblock. Specifically, if the UE receives an RB/RE level offset value fromthe PBCH payload corresponding to frequency #X, the UE may interpret thecorresponding value as an offset value from a specific RE of an SS/PBCHblock on the synchronization raster (e.g., the first RE on the minimumRB index) to a specific RE of CORESET#0 (e.g., the first RE on theminimum RB index) in order to identify the locations of frequencyresources of CORESET#0 as in [Method #1]. If the UE receives an RB/RElevel offset value from the PBCH payload corresponding to frequency #X,the UE may interpret the corresponding value as an offset value from thechannel raster of a band to which frequency #X belongs to a specificfrequency resource (e.g., center frequency) of CORESET #0 in order toidentify the locations of frequency resources of CORESET#0 as in [Method#2]. Alternatively, if the UE receives one of a plurality of candidatesfrom the PBCH payload corresponding to frequency #X, the UE mayinterpret the corresponding value as an actual resource among theplurality of candidates for CORESET#0 frequency resource regionscorresponding to the 5150 and 5170 MHz band to which frequency #Xbelongs in order to identify the locations of frequency resources ofCORESET#0 as in [Method #3].

[Method #5] If the UE needs to decode the PBCH payload for an SS/PBCHblock other than the synchronization raster to determine the locationsof frequency resources of CORESET#0, there may be restrictions on centerfrequency resources where SS/PB CH block transmission is allowed, ratherthan the synchronization raster in consideration of the limited PBCHpayload. The interval between center frequencies where the SS/PBCH blocktransmission is allowed may be a PRB or a multiple of PRBs, where thePRB may be based on the 30 kHz SCS (or 15 kHz SCS). In this case, theoffset between the SS/PBCH block and CORESET#0 with an interval of oneor multiple PRBs may need to be signaled. If the number of valuesrequired for the corresponding signaling is less than or equal to 8, itmay be configured by the CORESET configuration in the MIB as shown inTable 11/12. If the number of values required for the correspondingsignaling is more than 8, it may be configured by some or all of thebits for the CORESET configuration and/or k_(SSB) value in the MIB.

[Method #6] If the UE needs to decode the PBCH payload for an SS/PBCHblock other than the synchronization raster to determine the locationsof frequency resources of CORESET#0, signaling of the value of N^(QCL)_(SSB) may be different from signaling of the SS/PBCH block transmittedin the synchronization raster in order to support that the centerfrequency value of the SS/PBCH block is located without any restrictionson the 15 kHz SCS granularity.

The N^(QCL) _(SSB) value indicates the QCL relationship betweendifferent candidate SSB indices. In the current NR-U, one of {1, 2, 4,8} is indicated by the PBCH payload based on a combination of (1) 1 bitof subCarrierSpacingCommon and (2) 1 bit of spare or the LSB 1 bit ofssb-SubcarrierOffset (see Table 6). The value of ssb-SubcarrierOffset isused to indicate the k_(SSB) value in FR1. In the current NR-U, sinceboth the synchronization raster and the channel raster are located atthe 30 kHz granularity, the LSB 1 bit of ssb-SubcarrierOffset indicatedin units of 15 kHz is redundant. Therefore, the corresponding LSB 1 bitmay be used to signal the N^(QCL) _(SSB) value.

However, for an SS/PBCH block having as the center frequency a frequencyresource other than the synchronization raster (e.g., SS/PBCH block forautomatic neighbor relations (ANR)), transmission may be allowed at any15 kHz granularity in the frequency domain. The ANR refers to a methodfor minimizing or eliminating manual work on neighbor information wheninstalling a new BS and optimizing the neighbor information. When thereis an SS/PBCH block for ANR in a cell, the UE may read the cell globalidentifier (CGI) of the cell from the SS/PBCH block and report the CGIto the BS. On the other hand, when there is an SS/PBCH block for non-ANRin the cell, the UE may only perform channel measurement for thecorresponding cell based on the SS/PBCH block. Since the channel rasterdefined in the 5 GHz band for the NR-U system is located on the 30 kHzgranularity, REs of CORESET #0 may also be located on the 30 kHzgranularity. Accordingly, if an SS/PBCH block is transmitted with the 15kHz granularity and CORESET #0 is transmitted with the 30 kHzgranularity, the LSB 1 bit of ssb-SubcarrierOffset may also be requiredfor signaling of k_(SSB). In this case, since there is a problem thatthe N^(QCL) _(SSB) value is not signaled by the LSB 1 bit ofssb-SubcarrierOffset, another method of signaling the N^(QCL) _(SSB)value is proposed. That is, for an SS/PBCH block transmitted based onthe synchronization raster, the N^(QCL) _(SSB) value may be signaled inthe same way as in Table 6, but for an SS/PBCH block having as thecenter frequency a frequency resource other than the synchronizationraster, the N^(QCL) _(SSB) value may be signaled according to Opt1 orOpt2.

Opt1: Instead of the LSB of ssb-SubcarrierOffset, the N^(QCL) _(SSB)value may be signaled by combining subCarrierSpacingCommon with otherbits in the PBCH payload.

Opt2: Signaling of the N^(QCL) _(SSB) value may be configured only with1 bit of subCarrierSpacingCommon.

Opt1 is a method of signaling the N^(QCL) _(SSB) value as shown in Table6 by combing 1 bit of the PBCH payload (e.g., MSB 1 bit of 4 bits ofpdcch-ConfigSIB1, 1 bit of dmrs-TypeA-Position, etc.) withsubCarrierSpacingCommon. The reason that the MSB 1 bit of the 4 bits ofpdcch-ConfigSIB1 is available is that 8 reserved states may not besignaled as shown in Table 9. In addition, if the 1 bit ofdmrs-TypeA-Position is used, the position of a type A DMRS needs to beassumed. When receiving a PDCCH/PDSCH for receiving SI corresponding toan SS/PBCH block having a frequency resource other than thesynchronization raster as the center frequency, the UE may assume thatthe first type A DMRS is always transmitted in the third (or fourth)symbol in a slot.

According to Opt2, when it is difficult to use an additional 1 bit ofthe PBCH payload, the N^(QCL) _(SSB) value may be signaled only bysubCarrierSpacingCommon as shown in Table 17. Table 17 shows a merelyexample of signaling, and actual values corresponding to scs15or60 andscs30or120 may be replaced by any one of 1, 2, 4, and 8.

TABLE 17 subCarrierSpacingCommon N^(QCL) _(SSB) scs15or60  1 [or 2]scs30or120 4 [or 8]

[Method #7] When the PBCH payload indicates that the N^(QCL) _(SSB)value is one of {1, 2, 4, 8} with a combination of 1 bit correspondingto subcarrierSpacingCommon and the LSB 1 bit of ssb-SubcarrierOffset(see Table 6), the LSB of k_(SSB) may need to be defined. Specifically,the LSB of k_(SSB) may be defined as 0 in the following cases: 1) whenthe center frequency of an SS/PBCH block is equal to the synchronizationraster; 2) when the center frequency of the SS/PBCH block is equal tothe channel raster; or 3) when the interval between the center frequencyof the SS/PBCH block and the channel/synchronization raster is aninteger multiple of 30 kHz. When the interval between the centerfrequency of the SS/PBCH block and the channel/synchronization raster isan integer multiple of 15 kHz (except for zero), the LSB of k_(SSB) maybe defined as ‘1’.

The interval of synchronization/channel rasters for the NR-U system inthe 5 GHz band is all defined as an integer multiple of 30 kHz. Thus, ifthe carrier bandwidth is configured by considering the channel raster asthe center frequency and if the SS/PBCH block and CORESET#0 aretransmitted/configured in a part of the corresponding bandwidth(centered on the synchronization raster), the interval between theminimum RE (e.g., first subcarrier) of CORESET#0 and the minimum RE(e.g., first subcarrier) of the SS/PBCH block must be an integermultiple of 30 kHz. Specifically, the RE/RB level interval between theminimum RE of CORESET #0 and the minimum RE of the SS/PBCH block may besignaled by the PBCH payload. Here, the RE level interval may beexpressed by 5 bits of k_(SSB) (i.e., MSB 1 bit of 3 bits included inthe MIB used for candidate SSB indices in FR2+4 bits ofssb-SubcarrierOffset). The RB level interval may be signaled based onCORESET configuration tables as described in [Method #1]. Specifically,a CRB grid may be generated by considering a point that is separated bythe RE level interval corresponding to k_(SSB) from the minimum RE ofthe SS/PBCH block as the reference point, and the location of theminimum RE of CORESET#0 may be determined by applying the RB leveloffset of the CORESET#0 configuration to the reference point (see FIG.11 ). In this case, considering that k_(SSB) corresponds to signaling atan interval of 15 kHz (that is, the number of subcarriers based onSCS=15 kHz) and in the NR-U system, the interval between the minimum REof CORESET#0 and the minimum RE of the SS/PBCH block (centered on thesynchronization raster) satisfies an integer multiple of 30 kHz, the LSB1 bit of ssb-SubcarrierOffset may always be ‘0’. Accordingly, thecorresponding value may be used for other purposes, for example, tosignal the value of N^(QCL) _(SSB).

However, as described in [Method #6], it may be necessary to find thelocation of CORESET#0 corresponding to SS/PBCH block that is notcentered on the synchronization raster (for the purpose of ANR). In thiscase, (1) if the center frequency of the SS/PBCH block is the same asthe channel raster or (2) if the interval between the center frequencyof the SS/PBCH block and the channel/synchronization raster is aninteger multiple of 30 kHz (e.g., 0, 30, 60, . . . ), the LSB of k_(SSB)may also be defined as ‘0’ (in the same way as when the SS/PBCH blocktransmitted in the synchronization raster) (for example, k_(SSB)=00000,00010, 00100, . . . ; xxxx0, where x=0 or 1). On the other hand, if theinterval between the center frequency of the SS/PBCH block not centeredon the synchronization raster and the channel/synchronization raster isnot an integer multiple of 30 kHz but an integer multiple of 15 kHz(except for zero) (e.g., 15, 45, . . . ), the LSB of k_(SSB) may bedefined as ‘1’ (for example, k_SSB=00001, 00011, . . . ; xxxx1, wherex=0 or 1). This is because the interval between each RE of CORESET #0and the channel raster may be maintained as an integer multiple of 30kHz to align the grid of CORESET#0 with the channel raster. Therefore,if the interval between the center frequency of the SS/PBCH block notcentered on the synchronization raster and the channel/synchronizationraster is not an integer multiple of 30 kHz but an integer multiple of15 kHz (except for zero), an odd value of k_(SSB) may be signaled (i.e.,a value of LSB=1).

In other words, when the PBCH payload indicates that the N^(QCL) _(SSB)value is one of {1, 2, 4, 8} with a combination of 1 bit correspondingto subcarrierSpacingCommon and the LSB 1 bit of ssb-SubcarrierOffset,

If the interval between the center frequency of the SS/PBCH block andthe channel/synchronization raster satisfy an integer multiple of 30 kHz(including zero), the LSB 1 bit of ssb-SubcarrierOffset (or k_(SSB)) maybe assumed to be ‘0’.

On the other hand, if the interval between the center frequency of theSS/PBCH block and the channel/synchronization raster does not satisfy aninteger multiple of 30 kHz (including zero) but satisfies an integermultiple of 15 kHz (except for zero), the LSB 1 bit ofssb-SubcarrierOffset (or k_(SSB)) may be assumed to be ‘1’.

The above proposals may be summarized as follows in conjunction withTable 6.

TABLE 18 LSB of ssb- LSB of ssb- SubcarrierOffset SubcarrierOffset(assumed value subCarrierSpacingCommon (actual value) N^(QCL) _(SSB) fork_SSB) scs15or60  0 1 0 for case A scs15or60  1 2 1 for case Bscs30or120 0 4 scs30or120 1 8 * Case A: The interval between the centerfrequency of the SS/PBCH block and the channel/synchronization raster isan integer multiple of 30 kHz (including zero). * Case B: The intervalbetween the center frequency of the SS/PBCH block and thechannel/synchronization raster is not an integer multiple of 30 kHz(including zero).

Alternatively, k_(SSB) may be defined as follows (see Table 19).

If the SS/PBCH block is detected on a licensed carrier: k_SSB=MSB 1 bitof 3 bits included in MIB used for candidate SSB indices+4 bits ofssb-SubcarrierOffset.

If the SS/PBCH block is detected in an unlicensed carrier: k_SSB=MSB 1bit of 3 bits of MIB used for candidate SSB indices+MSB 3 bits ofssb-SubcarrierOffset+X (where X=0 for case A or X=1 for case B; seeTable 9).

TABLE 19 Carrier LSB of k_SSB Licensed carrier LSB ofssb-SubcarrierOffset Unlicensed carrier 0 for case A (see, table 17)1for case B (see, table 17)

Licensed and unlicensed carriers may be identified according to thefrequency of the carrier in which the SS/PBCH block is detected, and theinterval with the channel/synchronization raster may be predefined foreach carrier (type) in specifications. Alternatively, even when the samefrequency is used, the carrier type (licensed or unlicensed carrier) mayvary depending on regions. In this case, the licensed and unlicensedcarriers may be identified by different PBCH payloads or CRC values. Toidentify the carrier type at the corresponding frequency, asynchronization raster for the licensed band and a synchronizationraster for the unlicensed band may be separately defined inspecifications. The UE may perform PDCCH monitoring by finding thelocation of CORESET#0 based on the value of k_(SSB). Also, the UE mayperform the operation of FIG. 9 based on the value of N^(QCL) _(SSB).

Additionally, this method may be applied only when the MSB 2 bits ofk_(SSB) (that is, the MSB 1 bit of 3 bits of the MIB used for candidateSSB indices in FR2 and the MSB 1 bit of 4 bits of ssb-SubcarrierOffset)are not ‘11’ in current Rel-15 NR. The reason for this is that in theRel-15 NR system, when the value of k_(SSB) is more than or equal to 24(that is, when each of the MSB 2 bits of k_(SSB) is ‘1’), the value ofk_(SSB) is used to inform the location of the nearest SS/PBCH block(including CORESET#0 information) because CORESET#0 is not provided inthe corresponding SS/PBCH block as shown in Table 20. In other words, inthe current Rel-15 NR system, if the MSB 2 bits of k_(SSB) (that is, theMSB 1 bit of 3 bits of the MIB used for candidate SSB indices in FR2 andthe MSB 1 bit of 4 bits of ssb-SubcarrierOffset) are ‘11’ (even forunlicensed bands), the LSB of ssb-SubcarrierOffset may be set to the LSBof k_(SSB) and then interpreted as in Table 20. On the other hand, ifthe MSB 2 bits of k_(SSB) are ‘00’, ‘10’, or ‘01’, the LSB of k_(SSB)may be configured according to the present method. Alternatively, if theMSB 2 bits of k_(SSB) are ‘11’ (even for unlicensed band), the LSB ofssb-SubcarrierOffset may be set to the LSB of k_(SSB) as in the currentRel-15 NR system. If the MSB 2 bits of k_(SSB) are ‘00’, ‘10’ or ‘01’,the LSB of k_(SSB) may be always set to ‘0’. The location of the SS/PBCHblock not centered on the synchronization raster (where the location ofCORESET#0 needs to be found for the purpose of ANR) may be restricted sothat the location is only a multiple of 30 kHz from the synchronizationraster.

TABLE 20 3GPP TS 38.213 Rel-15, Section 13 If a UE detects a firstSS/PBCH block and determines that a CORESET for Type0-PDCCH CSS set isnot present, and for 24≤k_(SSB)≤29 for FR1 or for 12≤k_(SSB)≤13 for FR2,the UE may determine the nearest (in the corresponding frequencydirection) global synchronization channel number (GSCN) of a secondSS/PBCH block having a CORESET for an associated Type0-PDCCH CSS set asN^(Reference) _(GSCN) + N^(Offset) _(GSCN). N^(Reference) _(GSCN) is theGSCN of the first SS/PBCH block and N^(Offset) _(GSCN) is a GSCN offsetprovided by a combination of k_(SSB) and controlResourceSetZero andsearchSpaceZero in pdcch-ConfigSIB1. If the UE detects the secondSS/PBCH block and the second SS/PBCH block does not provide a CORESETfor Type0-PDCCH CSS set, the UE may ignore the information related toGSCN of SS/PBCH block locations for performing cell search. If a UEdetects a SS/PBCH block and determines that a CORESET for Type0-PDCCHCSS set is not present, and for k_(SSB)=31 for FR1 or for k_(SSB)=15 forFR2, the UE determines that there is no SS/PBCH block having anassociated Type0-PDCCH CSS set within a GSCN range [N^(Reference)_(GSCN) − N^(Start) _(GSCN), N^(Reference) _(GSCN) + N^(End) _(GSCN)].N^(Start) _(GSCN) and N^(End) _(GSCN) are respectively determined bycontrolResourceSetZero and searchSpaceZero in pdcch- ConfigSIB1. If theGSCN range is [N^(Reference) _(GSCN), N^(Reference) _(GSCN)], the UEdetermines that there is no information for a second SS/PBCH block witha CORESET for an associated Type0- PDCCH CSS set on the detected SS/PBCHblock. If a UE does not detect any SS/PBCH block providing a CORESET forType0-PDCCH CSS set, within a time period determined by the UE, the UEmay ignore the information related to GSCN of SS/PBCH locations inperforming cell search.

FIG. 20 illustrates a signal transmission process according to anexample of the present disclosure. Referring to FIG. 20 , a UE maydetect an SSB in a cell (S2002). In this case, the SSB may include 15kHz-granularity-based offset information. The UE may determine asubcarrier offset used to identify a frequency position of a CORESETassociated with the SSB based on the 15 kHz-granularity-based offsetinformation (S2204). Thereafter, the UE may monitor the CORESETassociated with the SSB based on the subcarrier offset (S2206). In thiscase, based on detection of the SSB in an unlicensed band, (1) adifference between a synchronization raster in the unlicensed band andthe center frequency of the SSB may be limited to a multiple of 30 kHz,and/or (2) the subcarrier offset may indicate only a multiple of 30 kHzbased on the 15 kHz-granularity-based offset information.

In this case, based on the detection of the SSB in the unlicensed band,the subcarrier offset may indicate a multiple of 15 kHz. The 15kHz-granularity-based offset information may include 4 bits ofssb-SubcarrierOffset as least significant bits (LSBs). In addition,based on the detection of the SSB in the unlicensed band, the subcarrieroffset may be determined to be equal to a value obtained by setting oneLSB of the 15 kHz-granularity-based offset information to ‘0’. Further,based on the detection of the SSB in the unlicensed band, the one LSB ofthe 15 kHz-granularity-based offset information may be used to identifySSB candidates in a quasi-co-location (QCL) relationship.

2) Transmitter (Entity B) (e.g., BS)

[Method #1A] The BS may signal an offset value from a specific RE of anSS/PBCH block (e.g., the first RE in the minimum RB index) to a specificRE of CORESET#0 (e.g., the first RE in the minimum RB index) through thePBCH payload of the corresponding SS/PBCH block. In this case, theoffset value may be defined at the RB and/or RE level, and the RB leveloffset value may have a range (that varies depending on each frequencyband) determined based on the synchronization raster and channel rasterdefined for NR-U frequency bands. Here, the RE refers to a unit on thefrequency axis, and the order of REs may be equivalent to the order ofREs in one OFDM symbol. Accordingly, an RE may be replaced with asubcarrier.

When the UE attempts initial access in frequency bands of the NR-Usystem, the UE may expect an SS/PBCH and CORESET#0 with an SCS of 30kHz. In this case, the frequency-domain position and time-domainduration of CORESET#0 may be defined the same as those of the current NRsystem. Table 10 shows sets of RBs and slot symbols of CORESET for aType0-PDCCH search space set when the SCS of {SS/PBCH block, PDCCH} is{30, 30} kHz for frequency bands with a minimum channel bandwidth of 5or 10 MHz in the current NR system.

However, the following restrictions may be imposed in NR-U: the numberof RBs of 30 kHz CORESET#0 is 48, and the time-domain duration thereofis one or two (OFDM) symbols. In addition, the range of the RB leveloffset value may be determined by the synchronization raster and channelraster defined for NR-U frequency bands. For example, for a combinationof each band for operating the NR-U system and the carrier/BWPbandwidth, if the maximum/minimum of the RB level offset value betweenthe minimum RB index of the SS/PBCH block and the minimum RB index ofCORESET#0 is in the range of [A, B], some or all of the values between Aand B in the column corresponding to the offset of Table 10 may besignaled. For example, when A=−2 and B=5, 8 states among a total of 16states correspond to one symbol, and the remaining 8 states correspondto two symbols. Each of the 8 states may signal an RB level offset valuebetween −2 to 5. Additionally, the RE level offset value may be signaledby the value of k_(SSB) in the same way as in the NR system. Table 11shows the configuration of CORESET#0 in the case of A=−2 and B=5.

As an example, as shown in FIG. 13 , when the UE receives an SS/PBCHblock with a center frequency of 5155.68 MHz, which is thesynchronization raster defined for a 5150 to 5170 MHz band, the UE mayobtain ‘offset X’, which is a frequency offset between the SS/PBCH blockand CORESET#0, from the PBCH payload of the corresponding SS/PBCH block.For example, when the UE is signaled with index #4 of Table 11 andk_(SSB)=6 through the PBCH payload, the UE may recognize that thefrequency region of CORESET#0 starts from a position apart by 2 RBs and6 REs from the SS/PBCH block.

As another example, the frequency-domain position difference betweenRB#0 of the SS/PBCH block and RB#0 of 51 PRBs may be within 1 PRB asshown in FIG. 14 , and the frequency-domain position difference betweenRB#0 of the SS/PBCH block and RB#0 of 51 PRBs may be more than 4 PRBs asshown in FIG. 15 . For FIG. 14 , it may be preferable that the first PRBof CORESET#0 is aligned with the second PRB among the 51 PRBs inconsideration of interference with adjacent 20 MHz bands. In this case,−1 PRB may be required as the RB offset. Similarly, for FIG. 15 , it maybe preferable that the last PRB of CORESET#0 is aligned with the secondlast PRB among the 51 PRBs in consideration of interference withadjacent 20 MHz bands. In this case, 2 PRBs may be required as the RBoffset. To this end, information about RB offset values from a minimumof −1 PRB to a maximum of 2 PRBs needs to be configured. The locationsof the time/frequency-domain resources of CORESET#0 may be configured bythe PBCH payload according to a method shown in Table 12 above. In Table12, “reserved” states are to prepare for when an RB offset value that isnot in the range of [−1, 2] is required. Alternatively, RB offsets inthe range of [−k, k] (e.g., k=2) and reserved states may be signaled.

In addition, when the SS/PBCH block is transmitted based on the 15 kHzSCS, the number of RBs (or PRBs) may be set to 96, and the RB offset maybe set to values corresponding to twice the RB offset values based onthe 30 kHz SCS (in Table 12) as shown in Table 13. Alternatively, asshown in Table 14, the number of RBs (or PRBs) may be set to 96, and theRB offset may be determined by an RB granularity based on the 15 kHz SCSin addition to values corresponding to twice the RB offset values basedon the 30 kHz SCS (in Table 12). Alternatively, as shown in Table 15,the RB offset may be determined by values reflecting differences betweenabsolute frequency-domain resources corresponding to 20 PRBs of theSS/PBCH block in addition to values corresponding to twice the RB offsetvalues based on the 30 kHz SCS (in Table 12). That is, since the SS/PBCHblock consists of 20 PRBs regardless of SCSs, when the SCS is 15 kHz,frequency-domain resources may decrease (by 20 PRBs) compared to whenthe SCS is 30 kHz. Therefore, the RB offset values may be filled withvalues corresponding to {double of RB offset values based on 30 kHzSCS}+10 (because 10 PRBs are reduced with respect to the centerfrequency of the SS/PBCH block) (or with RB granularity values betweenthe minimum/maximum values of the corresponding values) as shown inTable 15.

Table 12 shows the configuration of CORESET#0 when the SS/PBCH block isbased on the 30 kHz SCS, and Tables 13 to 15 show the configurations ofCORESET#0 when the SS/PBCH block is based on the 15 kHz SCS. In thetables, a to d denote integers, respectively. The RB offset is definedbased on the SCS of a CORESET (i.e., CORESET#0) for a Type0-PDCCH CSSset. As shown in FIGS. 12 to 15 , the SCS of CORESET#0 is the same asthe SCS of the corresponding SS/PBCH block.

[Method #2A] An offset value from the channel raster corresponding to afrequency band in which an SS/PBCH block is transmitted to a specificfrequency resource (e.g., center frequency) of CORESET#0 may beconfigured by the PBCH payload of the corresponding SS/PBCH block. Inthis case, the offset value may be defined at the RB and/or RE level,and the RB level offset value may have a range (that varies depending oneach frequency band) determined based on the channel raster defined forNR-U frequency bands.

If channel raster candidates vary depending on coexistence with Wi-Fi,the channel raster in this proposal may mean a channel raster when thecoexistence with Wi-Fi is assumed. In addition, if channel rastercandidates vary according to the carrier/BWP bandwidth, the channelraster in this proposal may mean a channel raster when a specificcarrier bandwidth (e.g., 20 MHz) is assumed.

For example, for a combination of each band for NR-U operation and aspecific carrier bandwidth (e.g., 20 MHz), if the maximum/minimum of theRB level offset value from the channel raster to the specific frequencyresource (e.g., center frequency) of CORESET#0 is in the range of [A,B], some or all of the values between A and B in the columncorresponding to the offset of Table 10 may be signaled. For example,when A=−3 and B=4, 8 states among a total of 16 states correspond to onesymbol, and the remaining 8 states correspond to two symbols. Each ofthe 8 states may signal an RB level offset value between −3 to 4. Inaddition, the RE level offset value may be signaled by the value ofk_(SSB) in the same way as in the NR system. Table 16 shows theconfiguration of CORESET#0 in the case of A=−3 and B=4.

As an example, as shown in FIG. 16 , when the UE receives an SS/PBCHblock with a center frequency of 5155.68 MHz, which is thesynchronization raster defined for a 5150 to 5170 MHz band, the UE mayobtain an offset value between a specific channel raster value (e.g.,5160 MHz) defined in the corresponding band and the center frequency ofCORESET#0 from the PBCH payload of the corresponding SS/PBCH block. Forexample, when the UE is signaled with index #3 of Table 16 and k_(SSB)=0through the PBCH payload, the UE may identify the frequency resourceregion of CORESET#0 consisting of 48 PRBs with the channel raster as thecenter frequency.

As another example, when the offset value from the channel rastercorresponding to the frequency band in which the SS/PBCH block istransmitted to the specific frequency resource (e.g., center frequency)of CORESET#0 is configured by the PBCH payload of the SS/PBCH block,only the RE level offset value (except for the RB level offset) may besignaled as the corresponding offset value. That is, the centerfrequency of CORESET#0 may be aligned with the specific channel raster,and the RB grid of CORESET#0 may be aligned with the RB grid of thecarrier/BWP, which is managed by the BS in the corresponding frequencyband, by the k_(SSB) value. In this case, the k_(SSB) value may mean nRE offset(s) (in the lower frequency direction) with respect to thechannel raster, which is the reference point (in this case, n may be anegative number) or mean n RE offset(s) (in the higher frequencydirection) (in this case, n may be a positive number). For example, ifthe k_(SSB) value is between 1 and 12, it may mean RE offset(s) in thehigher frequency direction (for example, if k_(SSB)=n, it may mean n REoffset(s) in the higher frequency direction). If the k_(SSB) value isbetween 13 and 23, it may mean RE offset(s) in the lower frequencydirection (for example, if k_(SSB)=n, it may mean (n-12) RE offset(s) inthe lower frequency direction).

[Method #3A] Candidates may be defined for a plurality of CORESET#0frequency resource regions corresponding to a band in which an SS/PBCHblock is transmitted, and which one of the candidates is actually usedmay be configured by the PBCH payload of the corresponding SS/PBCHblock. In this case, the plurality of candidates for CORESET#0 frequencyresource regions may vary depending on the carrier/BWP bandwidth, thenumber of PRBs used in the carrier/BWP bandwidth, and/or the location ofa 20 MHz band in which the SS/PBCH block is transmitted in thecarrier/BWP bandwidth (for example, whether the SS/PBCH block is locatedat a higher 20 MHz band or a lower 20 MHz band of a 40 MHz carrierbandwidth). In addition, the RB grid as well as the location ofCORESET#0 may be informed by signaling.

For convenience, when a 20 MHz carrier is configured with 51 PRBs in the5150 to 5170 MHz band as shown in FIG. 16 , the offset value between theSS/PBCH block and CORESET#0 may be defined as offset X. When a 20 MHzcarrier is configured with 50 PRBs in the 5150 to 5170 MHz band as shownin FIG. 17 , the offset value between the SS/PBCH block and CORESET#0may be defined as offset Y. When a 40 MHz carrier is configured with 106PRBs in the 5150 to 5190 MHz band as shown in FIG. 18 , the offset valuebetween the SS/PBCH block and CORESET#0 may be defined as offset Z.

The BS may inform one of offsets X/Y/Z through the PBCH payload. Whenthe UE receives the SS/PBCH block with a center frequency of 5155.68MHz, which is the synchronization raster defined in the 5150 to 5170 MHzband, the UE may obtain one of offsets X/Y/Z from the PBCH payload ofthe corresponding SS/PBCH block. The UE may identify the location of theminimum RB of CORESET#0 by applying the received offset. This examplerelates to signaling of the offset value between the SS/PBCH block andCORESET#0, but an offset value between the channel raster and a specificfrequency resource (e.g., center frequency) of CORESET#0 may also besignaled as in [Method #2A]. In addition, the corresponding offset valuemay be defined/interpreted differently according to the frequency bandof the SS/PBCH block.

[Method #4A] If the UE needs to decode the PBCH payload for an SS/PBCHblock other than the synchronization raster to determine the locationsof frequency resources of CORESET#0, the UE may reinterpret informationin the decoded PBCH payload by assuming that the SS/PBCH block istransmitted in the synchronization raster defined for a bandcorresponding to the corresponding SS/PBCH block.

According to the following motivation, the BS may need to provideinformation on CORESET#0 frequency resources even for the SS/PBCH blockother than the synchronization raster.

Different operators may coexist in an unlicensed band, and the sameoperator may be in unplanned deployment environments, so the same(physical) cell ID may be used between cells in the same band. Toprevent the UE from being confused by this problem, the BS may need totransmit information about CORESET#0 and a type0-PDCCH CSS set forhigher layer signaling (e.g., SIB1) containing information on anoperator ID, a PLMN ID, or a global cell ID (even for an SS/PBCH blockthat is not transmitted in the synchronization raster). For example,assuming that gNB #X transmits an SS/PBCH block in frequency #X and UE#Y is associated with gNB #Y, gNB #Y may instruct UE #Y to performmeasurement on frequency #X (frequency #X may not match thesynchronization raster). After performing the measurement on frequency#X, UE #Y may report a discovered cell ID of gNB #X and the measurementresult of a corresponding cell to gNB #Y. If gNB #Y does not knowwhether gNB #X is the same operator, gNB #Y may instruct UE #Y to readhigher layer signaling (e.g., SIB1) containing information on theoperator ID, PLMN ID or global cell ID of gNB #X and report theinformation on the operator ID, PLMN ID, or global cell ID. Uponreceiving the corresponding information, gNB #Y may update the operatorinformation on gNB #X. Considering this operation, gNB #X transmittingthe SS/PBCH block in frequency #X may need to transmit information aboutCORESET#0 and a type0-PDCCH CSS set for scheduling a PDSCH carryinghigher layer signaling containing information on an operator ID, a PLMNID, or a global cell ID explicitly/implicitly in the SS/PBCH block (forconvenience, although such higher layer signaling is named SIB1, it maycorrespond to cell-common higher layer signaling).

For example, as shown in FIG. 19 , if the UE decodes the PBCH payload ofan SS/PBCH block having, as the center frequency, frequency #X ratherthan the synchronization raster, the BS may configure and transmit thecorresponding PBCH payload based on an SS/PBCH block having as thecenter frequency 5155.68 MHz, which is the synchronization rasterdefined for the 5150 to 5170 MHz band corresponding to the correspondingSS/PBCH block. Specifically, if the UE receives an RB/RE level offsetvalue from the PBCH payload corresponding to frequency #X, the UE mayinterpret the corresponding value as an offset value from a specific REof an SS/PBCH block on the synchronization raster (e.g., the first RE onthe minimum RB index) to a specific RE of CORESET#0 (e.g., the first REon the minimum RB index) in order to identify the locations of frequencyresources of CORESET#0 as in [Method #1A]. If the UE receives an RB/RElevel offset value from the PBCH payload corresponding to frequency #X,the UE may interpret the corresponding value as an offset value from thechannel raster of a band to which frequency #X belongs to a specificfrequency resource (e.g., center frequency) of CORESET #0 in order toidentify the locations of frequency resources of CORESET#0 as in [Method#2A]. Alternatively, if the UE receives one of a plurality of candidatesfrom the PBCH payload corresponding to frequency #X, the UE mayinterpret the corresponding value as an actual resource among theplurality of candidates for CORESET#0 frequency resource regionscorresponding to the 5150 and 5170 MHz band to which frequency #Xbelongs in order to identify the locations of frequency resources ofCORESET#0 as in [Method #3A].

[Method #5A] If the UE needs to decode the PBCH payload for an SS/PBCHblock other than the synchronization raster to determine the locationsof frequency resources of CORESET#0, there may be restrictions on centerfrequency resources where SS/PBCH block transmission is allowed, ratherthan the synchronization raster in consideration of the limited PBCHpayload. The interval between center frequencies where the SS/PBCH blocktransmission is allowed may be a PRB or a multiple of PRBs, where thePRB may be based on the 30 kHz SCS (or 15 kHz SCS). In this case, theoffset between the SS/PBCH block and CORESET#0 with an interval of oneor multiple PRBs may need to be signaled. If the number of valuesrequired for the corresponding signaling is less than or equal to 8, itmay be configured by the CORESET configuration in the MIB as shown inTable 11/12. If the number of values required for the correspondingsignaling is more than 8, it may be configured by some or all of thebits for the CORESET configuration and/or k_(SSB) value in the MIB.

[Method #6A] If the UE needs to decode the PBCH payload for an SS/PBCHblock other than the synchronization raster to determine the locationsof frequency resources of CORESET#0, signaling of the value of N^(QCL)_(SSB) may be different from signaling of the SS/PBCH block transmittedin the synchronization raster in order to support that the centerfrequency value of the SS/PBCH block is located without any restrictionson the 15 kHz SCS granularity.

The N^(QCL) _(SSB) value indicates the QCL relationship betweendifferent candidate SSB indices. In the current NR-U, one of {1, 2, 4,8} is indicated by the PBCH payload based on a combination of (1) 1 bitof subCarrierSpacingCommon and (2) 1 bit of spare or LSB 1 bit ofssb-SubcarrierOffset (see Table 6). The value of ssb-SubcarrierOffset isused to indicate the k_(SSB) value in FR1. In the current NR-U, sinceboth the synchronization raster and the channel raster are located atthe 30 kHz granularity, the LSB 1 bit of ssb-SubcarrierOffset indicatedin units of 15 kHz is redundant. Therefore, the corresponding LSB 1 bitmay be used to signal the N^(QCL) _(SSB) value.

However, for an SS/PBCH block having as the center frequency a frequencyresource other than the synchronization raster (e.g., SS/PBCH block forANR), transmission may be allowed at any 15 kHz granularity in thefrequency domain. Since the channel raster defined in the 5 GHz band forthe NR-U system is located on the 30 kHz granularity, REs of CORESET #0may also be located on the 30 kHz granularity. Accordingly, if anSS/PBCH block is transmitted with the 15 kHz granularity and CORESET #0is transmitted with the 30 kHz granularity, the LSB 1 bit ofssb-SubcarrierOffset may also be required for signaling of k_(SSB). Inthis case, since there is a problem that the N^(QCL) _(SSB) value is notsignaled by the LSB 1 bit of ssb-SubcarrierOffset, another method ofsignaling the N^(QCL) _(SSB) value is proposed. That is, for an SS/PBCHblock transmitted based on the synchronization raster, the N^(QCL)_(SSB) value may be signaled in the same way as in Table 6, but for anSS/PBCH block having as the center frequency a frequency resource otherthan the synchronization raster, the N^(QCL) _(SSB) value may besignaled according to Opt1 or Opt2.

Opt1: Instead of the LSB of ssb-SubcarrierOffset, the N^(QCL) _(SSB)value may be signaled by combining subCarrierSpacingCommon with otherbits in the PBCH payload.

Opt2: Signaling of the N^(QCL) _(SSB) value may be configured only with1 bit of subCarrierSpacingCommon.

Opt1 is a method of signaling the N^(QCL) _(SSB) value as shown in Table6 by combing 1 bit of the PBCH payload (e.g., MSB 1 bit of 4 bits ofpdcch-ConfigSIB1, 1 bit of dmrs-TypeA-Position, etc.) withsubCarrierSpacingCommon. The reason the MSB 1 bit of the 4 bits ofpdcch-ConfigSIB1 is available is that 8 reserved states may not besignaled as shown in Table 9. In addition, if the 1 bit ofdmrs-TypeA-Position is used, the position of a type A DMRS needs to beassumed. If the UE receives a PDCCH/PDSCH for receiving SI correspondingto an SS/PBCH block having a frequency resource other than thesynchronization raster as the center frequency, the BS may alwaystransmit the first type A DMRS in the third (or fourth) symbol in aslot.

According to Opt2, when it is difficult to use an additional 1 bit ofthe PBCH payload, the N^(QCL) _(SSB) value may be signaled only bysubCarrierSpacingCommon as shown in Table 17. Table 17 shows a merelyexample of signaling, and actual values corresponding to scs15or60 andscs30or120 may be replaced by any one of 1, 2, 4, and 8.

[Method #7A] When the PBCH payload indicates that the N^(QCL) _(SSB)value is one of {1, 2, 4, 8} with a combination of 1 bit ofsubcarrierSpacingCommon and the LSB 1 bit of ssb-SubcarrierOffset (seeTable 6), the LSB of k_(SSB) may need to be defined. Specifically, theLSB of k_(SSB) may be defined as 0 in the following cases: 1) when thecenter frequency of an SS/PBCH block is equal to the synchronizationraster; 2) when the center frequency of the SS/PBCH block is equal tothe channel raster; and 3) when the interval between the centerfrequency of the SS/PBCH block and the channel/synchronization raster isan integer multiple of 30 kHz. When the interval between the centerfrequency of the SS/PBCH block and the channel/synchronization raster isan integer multiple of 15 kHz (except for zero), the LSB of k_(SSB) maybe defined as ‘1’.

The interval of synchronization/channel rasters for the NR-U system inthe 5 GHz band is all defined as an integer multiple of 30 kHz. Thus, ifthe carrier bandwidth is configured by considering the channel raster asthe center frequency and if the SS/PBCH block and CORESET#0 aretransmitted/configured in a part of the corresponding bandwidth(centered on the synchronization raster), the interval between theminimum RE (e.g., first subcarrier) of CORESET#0 and the minimum RE(e.g., first subcarrier) of the SS/PBCH block may be an integer multipleof 30 kHz. Specifically, the RE/RB level interval between the minimum REof CORESET #0 and the minimum RE of the SS/PBCH block may be signaled bythe PBCH payload. Here, the RE level interval may be expressed by 5 bitsof k_(SSB) (i.e., MSB 1 bit of 3 bits of the MIB used for candidate SSBindices in FR2+4 bits of ssb-SubcarrierOffset). The RB level intervalmay be signaled based on CORESET configuration tables as described in[Method #1A]. Specifically, a CRB grid may be created by considering asthe reference point a point that is separated by the RE level intervalcorresponding to k_(SSB) from the minimum RE of the SS/PBCH block, andthe location of the minimum RE of CORESET#0 may be determined byapplying the RB level offset in the CORESET#0 configuration to thereference point (see FIG. 11 ). In this case, considering that k_(SSB)corresponds to signaling at an interval of 15 kHz (that is, the numberof subcarriers based on SCS=15 kHz) and in the NR-U system, the intervalbetween the minimum RE of CORESET#0 and the minimum RE of the SS/PBCHblock (centered on the synchronization raster) satisfies an integermultiple of 30 kHz, the LSB 1 bit of ssb-SubcarrierOffset may always be‘0’. Accordingly, the corresponding value may be used for otherpurposes, for example, to signal the value of N^(QCL) _(SSB).

However, as described in [Method #6A], for the SS/PBCH block that is notcentered on the synchronization raster (for the purpose of ANR), it maybe necessary to find the location of CORESET#0 related thereto. In thiscase, (1) if the center frequency of the SS/PBCH block is the same asthe channel raster and/or (2) if the interval between the centerfrequency of the SS/PBCH block and the channel/synchronization raster isan integer multiple of 30 kHz (e.g., 0, 30, 60, . . . ), the LSB ofk_(SSB) may also be defined as ‘0’ (in the same way as when the SS/PBCHblock is transmitted in the synchronization raster) (for example,k_(SSB)=00000, 00010, 00100, . . . ; xxxx0, where x=0 or 1). On theother hand, if the interval between the center frequency of the SS/PBCHblock not centered on the synchronization raster and thechannel/synchronization raster is not an integer multiple of 30 kHz butan integer multiple of 15 kHz (except for zero) (e.g., 15, 45, . . . ),the LSB of k_(SSB) may be defined as ‘1’ (for example, k_SSB=00001,00011, . . . ; xxxx1, where x=0 or 1). This is because the intervalbetween each RE of CORESET #0 and the channel raster may be maintainedas an integer multiple of 30 kHz to align the grid of CORESET#0 with thechannel raster. Therefore, if the interval between the center frequencyof the SS/PBCH block not centered on the synchronization raster and thechannel/synchronization raster is not an integer multiple of 30 kHz butan integer multiple of 15 kHz (except for zero), an odd value of k_(SSB)may be signaled (i.e., LSB=1).

In other words, when the PBCH payload indicates that the N^(QCL) _(SSB)value is one of {1, 2, 4, 8} with a combination of 1 bit ofsubcarrierSpacingCommon and the LSB 1 bit of ssb-SubcarrierOffset,

If the interval between the center frequency of the SS/PBCH block andthe channel/synchronization raster satisfies an integer multiple of 30kHz (including zero), the LSB 1 bit of ssb-SubcarrierOffset (or k_(SSB))may be assumed to be ‘0’.

On the other hand, if the interval between the center frequency of theSS/PBCH block and the channel/synchronization raster does not satisfy aninteger multiple of 30 kHz (including zero) but satisfies an integermultiple of 15 kHz (except for zero), the LSB 1 bit ofssb-SubcarrierOffset (or k_(SSB)) may be assumed to be ‘1’. The aboveproposals may be summarized as follows in conjunction with Table 6.

Alternatively, k_(SSB) may be defined as follows (see Table 19).

If the SS/PBCH block is detected on a licensed carrier: k_SSB=MSB 1 bitof 3 bits of MIB used for candidate SSB indices+4 bits ofssb-SubcarrierOffset.

If the SS/PBCH block is detected in an unlicensed carrier: k_SSB=MSB 1bit of 3 bits of MIB used for candidate SSB indices+MSB 3 bits ofssb-SubcarrierOffset+X (where X=0 for case A or X=1 for case B; seeTable 9).

Licensed and unlicensed carriers may be identified according to thefrequency of the carrier in which the SS/PBCH block is detected, and theinterval with the channel/synchronization raster may be predefined foreach carrier (type) in specifications. The BS may transmit a PDCCH atthe location of CORESET #0 based on k_(SSB). Alternatively, even whenthe same frequency is used, the carrier type (licensed or unlicensedcarrier) may vary depending on regions. In this case, the licensed andunlicensed carriers may be identified by different PBCH payloads or CRCvalues. To identify the carrier type at the corresponding frequency, asynchronization raster for the licensed band and a synchronizationraster for the unlicensed band may be separately defined inspecifications. Also, the BS may perform the operation of FIG. 9 basedon the value of N^(QCL) _(SSB).

Additionally, this method may be applied only when the MSB 2 bits ofk_(SSB) (that is, the MSB 1 bit of 3 bits of the MIB used for candidateSSB indices in FR2 and the MSB 1 bit of 4 bits of ssb-SubcarrierOffset)are not ‘11’ in current Rel-15 NR. The reason for this is that in theRel-15 NR system, when the value of k_(SSB) is more than or equal to 24(that is, when each of the MSB 2 bits of k_(SSB) is ‘1’), the value ofk_(SSB) is used to inform the location of the nearest SS/PBCH block(including CORESET#0 information) because CORESET#0 is not provided inthe corresponding SS/PBCH block as shown in Table 20. In other words, inthe current Rel-15 NR system, if the MSB 2 bits of k_(SSB) (that is, theMSB 1 bit of 3 bits of the MIB used for candidate SSB indices in FR2 andthe MSB 1 bit of 4 bits of ssb-SubcarrierOffset) are ‘11’ (even forunlicensed bands), the LSB of ssb-SubcarrierOffset may be set to the LSBof k_(SSB) and then interpreted as in Table 20. On the other hand, ifthe MSB 2 bits of k_(SSB) are ‘00’, ‘10’, or ‘01’, the LSB of k_(SSB)may be configured according to the present method. Alternatively, if theMSB 2 bits of k_(SSB) are ‘11’ (even for unlicensed band), the LSB ofssb-SubcarrierOffset may be set to the LSB of k_(SSB) as in the currentRel-15 NR system. If the MSB 2 bits of k_(SSB) are ‘00’, ‘10’ or ‘01’,the LSB of k_(SSB) may be always set to ‘0’. The location of the SS/PBCHblock not centered on the synchronization raster (where the location ofCORESET#0 needs to be found for the purpose of ANR) may be restricted sothat the location is only a multiple of 30 kHz from the synchronizationraster.

3) Receiver & Transmitter (Between Receiver and Transmitter)

According to the proposals of the present disclosure, a BS operating ina bandwidth of 5 or 6 GHz may transmit an SS/PBCH block by consideringas the center frequency a synchronization raster defined in thecorresponding bandwidth and transmit information on frequency resourcesof CORESET #0 through the PBCH payload of the corresponding SS/PBCHblock (S2102) as shown in FIG. 21 . Upon receiving the SS/PBCH block, aUE may identify the frequency resource region of CORESET#0 by analyzinga bandwidth in which the SS/PBCH block is detected and/or the PBCHpayload (e.g., CORESET configuration (pdcch-ConfigSIB1), k_(SSB), orother information) of the SS/PBCH block (S2104). In addition, the UE mayobtain information on a type0-PDCCH monitoring occasion by interpretingthe PBCH payload (e.g., pdcch-ConfigSIB1) in the SS/PBCH block.Thereafter, the UE may receive a PDCCH in the frequency resource regionof CORESET#0 on the type0-PDCCH monitoring occasion and obtain SI (e.g.,SIB1) from a PDSCH scheduled by the corresponding PDCCH.

Alternatively, according to the proposals of the present disclosure,even when a BS transmits an SS/PBCH block having as the center frequencya frequency that is not defined as a synchronization raster in anunlicensed band for the purpose of ANR, the corresponding SS/PBCH blockmay carry information on CORESET#0 and/or information on a type0-PDCCHmonitoring occasion (S2202) as shown in FIG. 22 . When applying PBCHinformation obtained from the corresponding bandwidth and detectedSS/PBCH block, a UE may assume that the received SS/PBCH block is anSS/PBCH block transmitted in a synchronization raster in a bandwidth towhich the corresponding SS/PBCH block belongs and interpret that thecorresponding SS/PBCH block is transmitted in the synchronization rasterin order to obtain the information on CORESET#0 and/or the informationon the type0-PDCCH monitoring occasion (S2204). Thereafter, the UE mayreceive a PDCCH in the frequency resource region of CORESET#0 on thetype0-PDCCH monitoring occasion and obtain SI (e.g., SIB1) from a PDSCHscheduled by the corresponding PDCCH.

In the proposals of the present disclosure, the 5 or 6 GHz band may bereplaced with an unlicensed band/UCell. In addition, the proposals ofthe present disclosure may be considered as methods ofconfiguring/interpreting MIB information related to CORESET#0differently according to the type of a frequency band (or cell) in whichan SS/PBCH block is detected. For example, according to Method #1, a UEmay obtain pdcch-ConfigSIB1 from an MIB after detecting an SS/PBCHblock. Thereafter, the UE may interpret pdcch-ConfigSIB1 differentlydepending on whether the frequency band (or cell) in which the SS/PBCHblock is detected is a licensed band/LCell or an unlicensed band/UCell.For example, the UE may interpret the MSB 4 bits of pdcch-ConfigSIB1 asfollows.

TABLE 21 Index Licensed band/LCell Unlicensed band/UCell 0 Offset0 forLCell Offset0 for UCell 1 Offset1 for LCell Offset1 for UCell . . . . .. . . . 15 Offset15 for LCell  Offset15 for UCell 

* Table 21 shows CORESET#0 configuration information. The CORESET#0configuration information may further include, for example, at least oneof a multiplexing pattern, the number of RB s, and/or the number ofsymbols. * An Offset for LCell and an offset for UCell may be configuredindependently. For example, the offset for LCell may be defined based on3GPP TS 38.213 Tables 13-11 to 13-15, and the offset for UCell may bedefined according to the proposals of the present disclosure inconsideration of a channel/synchronization raster.

The various descriptions, functions, procedures, proposals, methods,and/or operational flowcharts proposals of the present disclosuredescribed above in this document may be applied to, without beinglimited to, a variety of fields requiring wirelesscommunication/connection (e.g., 5G) between devices.

Hereinafter, a description will be given in more detail with referenceto the drawings. In the following drawings/description, the samereference symbols may denote the same or corresponding hardware blocks,software blocks, or functional blocks unless described otherwise.

FIG. 23 illustrates a communication system 1 applied to the presentdisclosure.

Referring to FIG. 23 , a communication system 1 applied to the presentdisclosure includes wireless devices, Base Stations (BSs), and anetwork. Herein, the wireless devices represent devices performingcommunication using Radio Access Technology (RAT) (e.g., 5G New RAT(NR)) or Long-Term Evolution (LTE)) and may be referred to ascommunication/radio/5G devices. The wireless devices may include,without being limited to, a robot 100 a, vehicles 100 b-1 and 100 b-2,an eXtended Reality (XR) device 100 c, a hand-held device 100 d, a homeappliance 100 e, an Internet of Things (IoT) device 100 f, and anArtificial Intelligence (AI) device/server 400. For example, thevehicles may include a vehicle having a wireless communication function,an autonomous driving vehicle, and a vehicle capable of performingcommunication between vehicles. Herein, the vehicles may include anUnmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may includean Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) deviceand may be implemented in the form of a Head-Mounted Device (HMD), aHead-Up Display (HUD) mounted in a vehicle, a television, a smartphone,a computer, a wearable device, a home appliance device, a digitalsignage, a vehicle, a robot, etc. The hand-held device may include asmartphone, a smartpad, a wearable device (e.g., a smartwatch or asmartglasses), and a computer (e.g., a notebook). The home appliance mayinclude a TV, a refrigerator, and a washing machine. The IoT device mayinclude a sensor and a smartmeter. For example, the BSs and the networkmay be implemented as wireless devices and a specific wireless device200 a may operate as a BS/network node with respect to other wirelessdevices.

The wireless devices 100 a to 100 f may be connected to the network 300via the BSs 200. An AI technology may be applied to the wireless devices100 a to 100 f and the wireless devices 100 a to 100 f may be connectedto the AI server 400 via the network 300. The network 300 may beconfigured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g.,NR) network. Although the wireless devices 100 a to 100 f maycommunicate with each other through the BSs 200/network 300, thewireless devices 100 a to 100 f may perform direct communication (e.g.,sidelink communication) with each other without passing through the BSs/network. For example, the vehicles 100 b-1 and 100 b-2 may performdirect communication (e.g. Vehicle-to-Vehicle(V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g.,a sensor) may perform direct communication with other IoT devices (e.g.,sensors) or other wireless devices 100 a to 100 f.

Wireless communication/connections 150 a, 150 b, or 150 c may beestablished between the wireless devices 100 a to 100 f/BS 200, or BS200/BS 200. Herein, the wireless communication/connections may beestablished through various RATs (e.g., 5G NR) such as uplink/downlinkcommunication 150 a, sidelink communication 150 b (or, D2Dcommunication), or inter BS communication (e.g. relay, Integrated AccessBackhaul (IAB)). The wireless devices and the BSs/the wireless devicesmay transmit/receive radio signals to/from each other through thewireless communication/connections 150 a and 150 b. For example, thewireless communication/connections 150 a and 150 b may transmit/receivesignals through various physical channels. To this end, at least a partof various configuration information configuring processes, varioussignal processing processes (e.g., channel encoding/decoding,modulation/demodulation, and resource mapping/demapping), and resourceallocating processes, for transmitting/receiving radio signals, may beperformed based on the various proposals of the present disclosure.

FIG. 24 illustrates wireless devices applicable to the presentdisclosure.

Referring to FIG. 24 , a first wireless device 100 and a second wirelessdevice 200 may transmit radio signals through a variety of RATs (e.g.,LTE and NR). Herein, {the first wireless device 100 and the secondwireless device 200} may correspond to {the wireless device 100 x andthe BS 200} and/or {the wireless device 100 x and the wireless device100 x} of FIG. 23 .

The first wireless device 100 may include one or more processors 102 andone or more memories 104 and additionally further include one or moretransceivers 106 and/or one or more antennas 108. The processor(s) 102may control the memory(s) 104 and/or the transceiver(s) 106 and may beconfigured to implement the descriptions, functions, procedures,proposals, methods, and/or operational flowcharts disclosed in thisdocument. For example, the processor(s) 102 may process informationwithin the memory(s) 104 to generate first information/signals and thentransmit radio signals including the first information/signals throughthe transceiver(s) 106. The processor(s) 102 may receive radio signalsincluding second information/signals through the transceiver 106 andthen store information obtained by processing the secondinformation/signals in the memory(s) 104. The memory(s) 104 may beconnected to the processor(s) 102 and may store a variety of informationrelated to operations of the processor(s) 102. For example, thememory(s) 104 may store software code including commands for performinga part or the entirety of processes controlled by the processor(s) 102or for performing the descriptions, functions, procedures, proposals,methods, and/or operational flowcharts disclosed in this document.Herein, the processor(s) 102 and the memory(s) 104 may be a part of acommunication modem/circuit/chip designed to implement RAT (e.g., LTE orNR). The transceiver(s) 106 may be connected to the processor(s) 102 andtransmit and/or receive radio signals through one or more antennas 108.Each of the transceiver(s) 106 may include a transmitter and/or areceiver. The transceiver(s) 106 may be interchangeably used with RadioFrequency (RF) unit(s). In the present disclosure, the wireless devicemay represent a communication modem/circuit/chip.

The second wireless device 200 may include one or more processors 202and one or more memories 204 and additionally further include one ormore transceivers 206 and/or one or more antennas 208. The processor(s)202 may control the memory(s) 204 and/or the transceiver(s) 206 and maybe configured to implement the descriptions, functions, procedures,proposals, methods, and/or operational flowcharts disclosed in thisdocument. For example, the processor(s) 202 may process informationwithin the memory(s) 204 to generate third information/signals and thentransmit radio signals including the third information/signals throughthe transceiver(s) 206. The processor(s) 202 may receive radio signalsincluding fourth information/signals through the transceiver(s) 106 andthen store information obtained by processing the fourthinformation/signals in the memory(s) 204. The memory(s) 204 may beconnected to the processor(s) 202 and may store a variety of informationrelated to operations of the processor(s) 202. For example, thememory(s) 204 may store software code including commands for performinga part or the entirety of processes controlled by the processor(s) 202or for performing the descriptions, functions, procedures, proposals,methods, and/or operational flowcharts disclosed in this document.Herein, the processor(s) 202 and the memory(s) 204 may be a part of acommunication modem/circuit/chip designed to implement RAT (e.g., LTE orNR). The transceiver(s) 206 may be connected to the processor(s) 202 andtransmit and/or receive radio signals through one or more antennas 208.Each of the transceiver(s) 206 may include a transmitter and/or areceiver. The transceiver(s) 206 may be interchangeably used with RFunit(s). In the present disclosure, the wireless device may represent acommunication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices 100 and 200 willbe described more specifically. One or more protocol layers may beimplemented by, without being limited to, one or more processors 102 and202. For example, the one or more processors 102 and 202 may implementone or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP,RRC, and SDAP). The one or more processors 102 and 202 may generate oneor more Protocol Data Units (PDUs) and/or one or more Service Data Unit(SDUs) according to the descriptions, functions, procedures, proposals,methods, and/or operational flowcharts disclosed in this document. Theone or more processors 102 and 202 may generate messages, controlinformation, data, or information according to the descriptions,functions, procedures, proposals, methods, and/or operational flowchartsdisclosed in this document. The one or more processors 102 and 202 maygenerate signals (e.g., baseband signals) including PDUs, SDUs,messages, control information, data, or information according to thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document and provide thegenerated signals to the one or more transceivers 106 and 206. The oneor more processors 102 and 202 may receive the signals (e.g., basebandsignals) from the one or more transceivers 106 and 206 and acquire thePDUs, SDUs, messages, control information, data, or informationaccording to the descriptions, functions, procedures, proposals,methods, and/or operational flowcharts disclosed in this document.

The one or more processors 102 and 202 may be referred to ascontrollers, microcontrollers, microprocessors, or microcomputers. Theone or more processors 102 and 202 may be implemented by hardware,firmware, software, or a combination thereof. As an example, one or moreApplication Specific Integrated Circuits (ASICs), one or more DigitalSignal Processors (DSPs), one or more Digital Signal Processing Devices(DSPDs), one or more Programmable Logic Devices (PLDs), or one or moreField Programmable Gate Arrays (FPGAs) may be included in the one ormore processors 102 and 202. The descriptions, functions, procedures,proposals, methods, and/or operational flowcharts disclosed in thisdocument may be implemented using firmware or software and the firmwareor software may be configured to include the modules, procedures, orfunctions. Firmware or software configured to perform the descriptions,functions, procedures, proposals, methods, and/or operational flowchartsdisclosed in this document may be included in the one or more processors102 and 202 or stored in the one or more memories 104 and 204 so as tobe driven by the one or more processors 102 and 202. The descriptions,functions, procedures, proposals, methods, and/or operational flowchartsdisclosed in this document may be implemented using firmware or softwarein the form of code, commands, and/or a set of commands.

The one or more memories 104 and 204 may be connected to the one or moreprocessors 102 and 202 and store various types of data, signals,messages, information, programs, code, instructions, and/or commands.The one or more memories 104 and 204 may be configured by Read-OnlyMemories (ROMs), Random Access Memories (RAMs), Electrically ErasableProgrammable Read-Only Memories (EPROMs), flash memories, hard drives,registers, cash memories, computer-readable storage media, and/orcombinations thereof. The one or more memories 104 and 204 may belocated at the interior and/or exterior of the one or more processors102 and 202. The one or more memories 104 and 204 may be connected tothe one or more processors 102 and 202 through various technologies suchas wired or wireless connection.

The one or more transceivers 106 and 206 may transmit user data, controlinformation, and/or radio signals/channels, mentioned in the methodsand/or operational flowcharts of this document, to one or more otherdevices. The one or more transceivers 106 and 206 may receive user data,control information, and/or radio signals/channels, mentioned in thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document, from one or moreother devices. For example, the one or more transceivers 106 and 206 maybe connected to the one or more processors 102 and 202 and transmit andreceive radio signals. For example, the one or more processors 102 and202 may perform control so that the one or more transceivers 106 and 206may transmit user data, control information, or radio signals to one ormore other devices. The one or more processors 102 and 202 may performcontrol so that the one or more transceivers 106 and 206 may receiveuser data, control information, or radio signals from one or more otherdevices. The one or more transceivers 106 and 206 may be connected tothe one or more antennas 108 and 208 and the one or more transceivers106 and 206 may be configured to transmit and receive user data, controlinformation, and/or radio signals/channels, mentioned in thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document, through the one ormore antennas 108 and 208. In this document, the one or more antennasmay be a plurality of physical antennas or a plurality of logicalantennas (e.g., antenna ports). The one or more transceivers 106 and 206may convert received radio signals/channels etc. from RF band signalsinto baseband signals in order to process received user data, controlinformation, radio signals/channels, etc. using the one or moreprocessors 102 and 202. The one or more transceivers 106 and 206 mayconvert the user data, control information, radio signals/channels, etc.processed using the one or more processors 102 and 202 from the baseband signals into the RF band signals. To this end, the one or moretransceivers 106 and 206 may include (analog) oscillators and/orfilters.

In the present disclosure, at least one memory (e.g., 104 or 204) maystore instructions or programs which, when executed, cause at least oneprocessor operably coupled to the at least one memory to performoperations according to some embodiments or implementations of thepresent disclosure.

In the present disclosure, a computer-readable storage medium may storeat least one instruction or computer program which, when executed by atleast one processor, causes the at least one processor to performoperations according to some embodiments or implementations of thepresent disclosure.

In the present disclosure, a processing device or apparatus may includeat least one processor and at least one computer memory coupled to theat least one processor. The at least one computer memory may storeinstructions or programs which, when executed, cause the at least oneprocessor operably coupled to the at least one memory to performoperations according to some embodiments or implementations of thepresent disclosure.

FIG. 25 illustrates another example of a wireless device applied to thepresent disclosure. The wireless device may be implemented in variousforms according to a use-case/service (refer to FIG. 23 ).

Referring to FIG. 25 , wireless devices 100 and 200 may correspond tothe wireless devices 100 and 200 of FIG. 24 and may be configured byvarious elements, components, units/portions, and/or modules. Forexample, each of the wireless devices 100 and 200 may include acommunication unit 110, a control unit 120, a memory unit 130, andadditional components 140. The communication unit may include acommunication circuit 112 and transceiver(s) 114. For example, thecommunication circuit 112 may include the one or more processors 102 and202 and/or the one or more memories 104 and 204 of FIG. 24 . Forexample, the transceiver(s) 114 may include the one or more transceivers106 and 206 and/or the one or more antennas 108 and 208 of FIG. 24 . Thecontrol unit 120 is electrically connected to the communication unit110, the memory 130, and the additional components 140 and controlsoverall operation of the wireless devices. For example, the control unit120 may control an electric/mechanical operation of the wireless devicebased on programs/code/commands/information stored in the memory unit130. The control unit 120 may transmit the information stored in thememory unit 130 to the exterior (e.g., other communication devices) viathe communication unit 110 through a wireless/wired interface or store,in the memory unit 130, information received through the wireless/wiredinterface from the exterior (e.g., other communication devices) via thecommunication unit 110.

The additional components 140 may be variously configured according totypes of wireless devices. For example, the additional components 140may include at least one of a power unit/battery, input/output (I/O)unit, a driving unit, and a computing unit. The wireless device may beimplemented in the form of, without being limited to, the robot (100 aof FIG. 23 ), the vehicles (100 b-1 and 100 b-2 of FIG. 23 ), the XRdevice (100 c of FIG. 23 ), the hand-held device (100 d of FIG. 23 ),the home appliance (100 e of FIG. 23 ), the IoT device (100 f of FIG. 23), a digital broadcast terminal, a hologram device, a public safetydevice, an MTC device, a medicine device, a fintech device (or a financedevice), a security device, a climate/environment device, the AIserver/device (400 of FIG. 23 ), the BSs (200 of FIG. 23 ), a networknode, etc. The wireless device may be used in a mobile or fixed placeaccording to a use-example/service.

In FIG. 25 , the entirety of the various elements, components,units/portions, and/or modules in the wireless devices 100 and 200 maybe connected to each other through a wired interface or at least a partthereof may be wirelessly connected through the communication unit 110.For example, in each of the wireless devices 100 and 200, the controlunit 120 and the communication unit 110 may be connected by wire and thecontrol unit 120 and first units (e.g., 130 and 140) may be wirelesslyconnected through the communication unit 110. Each element, component,unit/portion, and/or module within the wireless devices 100 and 200 mayfurther include one or more elements. For example, the control unit 120may be configured by a set of one or more processors. As an example, thecontrol unit 120 may be configured by a set of a communication controlprocessor, an application processor, an Electronic Control Unit (ECU), agraphical processing unit, and a memory control processor. As anotherexample, the memory 130 may be configured by a Random Access Memory(RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM)), a flash memory,a volatile memory, a non-volatile memory, and/or a combination thereof.

FIG. 26 illustrates a vehicle or an autonomous driving vehicle appliedto the present disclosure. The vehicle or autonomous driving vehicle maybe implemented by a mobile robot, a car, a train, a manned/unmannedAerial Vehicle (AV), a ship, etc.

Referring to FIG. 26 , a vehicle or autonomous driving vehicle 100 mayinclude an antenna unit 108, a communication unit 110, a control unit120, a driving unit 140 a, a power supply unit 140 b, a sensor unit 140c, and an autonomous driving unit 140 d. The antenna unit 108 may beconfigured as a part of the communication unit 110. The blocks110/130/140 a to 140 d correspond to the blocks 110/130/140 of FIG. 25 ,respectively.

The communication unit 110 may transmit and receive signals (e.g., dataand control signals) to and from external devices such as othervehicles, BSs (e.g., gNBs and road side units), and servers. The controlunit 120 may perform various operations by controlling elements of thevehicle or the autonomous driving vehicle 100. The control unit 120 mayinclude an Electronic Control Unit (ECU). The driving unit 140 a maycause the vehicle or the autonomous driving vehicle 100 to drive on aroad. The driving unit 140 a may include an engine, a motor, apowertrain, a wheel, a brake, a steering device, etc. The power supplyunit 140 b may supply power to the vehicle or the autonomous drivingvehicle 100 and include a wired/wireless charging circuit, a battery,etc. The sensor unit 140 c may acquire a vehicle state, ambientenvironment information, user information, etc. The sensor unit 140 cmay include an Inertial Measurement Unit (IMU) sensor, a collisionsensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor,a heading sensor, a position module, a vehicle forward/backward sensor,a battery sensor, a fuel sensor, a tire sensor, a steering sensor, atemperature sensor, a humidity sensor, an ultrasonic sensor, anillumination sensor, a pedal position sensor, etc. The autonomousdriving unit 140 d may implement technology for maintaining a lane onwhich a vehicle is driving, technology for automatically adjustingspeed, such as adaptive cruise control, technology for autonomouslydriving along a determined path, technology for driving by automaticallysetting a path if a destination is set, and the like.

For example, the communication unit 110 may receive map data, trafficinformation data, etc. from an external server. The autonomous drivingunit 140 d may generate an autonomous driving path and a driving planfrom the obtained data. The control unit 120 may control the drivingunit 140 a such that the vehicle or the autonomous driving vehicle 100may move along the autonomous driving path according to the driving plan(e.g., speed/direction control). In the middle of autonomous driving,the communication unit 110 may aperiodically/periodically acquire recenttraffic information data from the external server and acquiresurrounding traffic information data from neighboring vehicles. In themiddle of autonomous driving, the sensor unit 140 c may obtain a vehiclestate and/or surrounding environment information. The autonomous drivingunit 140 d may update the autonomous driving path and the driving planbased on the newly obtained data/information. The communication unit 110may transfer information about a vehicle position, the autonomousdriving path, and/or the driving plan to the external server. Theexternal server may predict traffic information data using AItechnology, etc., based on the information collected from vehicles orautonomous driving vehicles and provide the predicted trafficinformation data to the vehicles or the autonomous driving vehicles.

The above-described embodiments correspond to combinations of elementsand features of the present disclosure in prescribed forms. And, therespective elements or features may be considered as selective unlessthey are explicitly mentioned. Each of the elements or features can beimplemented in a form failing to be combined with other elements orfeatures. Moreover, it is able to implement an embodiment of the presentdisclosure by combining elements and/or features together in part. Asequence of operations explained for each embodiment of the presentdisclosure can be modified. Some configurations or features of oneembodiment can be included in another embodiment or can be substitutedfor corresponding configurations or features of another embodiment. And,it is apparently understandable that an embodiment is configured bycombining claims failing to have relation of explicit citation in theappended claims together or can be included as new claims by amendmentafter filing an application.

Those skilled in the art will appreciate that the present disclosure maybe carried out in other specific ways than those set forth hereinwithout departing from the spirit and essential characteristics of thepresent disclosure. The above embodiments are therefore to be construedin all aspects as illustrative and not restrictive. The scope of thedisclosure should be determined by the appended claims and their legalequivalents, not by the above description, and all changes coming withinthe meaning and equivalency range of the appended claims are intended tobe embraced therein.

The present disclosure is applicable to user equipments, base stations,or other devices in a wireless mobile communication system.

What is claimed is:
 1. A method performed by a user equipment (UE) in awireless communication system, the method comprising: detecting asynchronization signal/physical broadcast channel (SS/PBCH) blockincluding 15 kHz subcarrier spacing-based offset information;determining a control resource set (CORESET) for Type0-physical downlinkcontrol channel (PDCCH) common search space (CSS) set based on theSS/PBCH block, wherein a subcarrier offset between the CORESET forType0-PDCCH CSS set and the SS/PBCH block is determined based on the 15kHz subcarrier spacing-based offset information; monitoring the CORESETfor Type0-PDCCH CSS set, wherein, based on the SS/PBCH block detected ina shared spectrum, a frequency of the SS/PBCH block is separated from asynchronization raster by k*30 kHz, where k is an integer greater thanor equal to zero, and one least significant bit (LSB) of the subcarrieroffset is ‘0’.
 2. The method of claim 1, wherein the subcarrier offsetindicates a multiple of 30 kHz.
 3. The method of claim 1, wherein 4 LSBsof the subcarrier offset are determined based on a higher-layerparameter, ssb-SubcarrierOffset.
 4. The method of claim 1, wherein basedon the SS/PBCH block being detected in the shared spectrum, the one LSBof the 15 kHz subcarrier spacing-based offset information is used toidentify SS/PBCH block candidates in a quasi-co-location (QCL)relationship.
 5. A user equipment (UE) for use in a wirelesscommunication system, the UE comprising: at least one processor; and atleast one computer memory operably connected to the at least oneprocessor and configured to, when executed, cause the at least oneprocessor to perform operations comprising: detecting a synchronizationsignal/physical broadcast channel (SS/PBCH) block including 15 kHzsubcarrier spacing-based offset information; determining a controlresource set (CORESET) for Type0-physical downlink control channel(PDCCH) common search space (CSS) set based on the SS/PBCH block,wherein a subcarrier offset between the CORESET for Type0-PDCCH CSS setand the SS/PBCH block is determined based on the 15 kHz subcarrierspacing-based offset information; monitoring the CORESET for Type0-PDCCHCSS set, wherein, based on the SS/PBCH block detected in a sharedspectrum, a frequency of the SS/PBCH block is separated from asynchronization raster by k*30 kHz, where k is an integer greater thanor equal to zero, and one least significant bit (LSB) of the subcarrieroffset is ‘0’.
 6. The UE of claim 5, wherein the subcarrier offsetindicates a multiple of 30 kHz.
 7. The UE of claim 5, wherein 4 LSBs ofthe subcarrier offset are determined based on a higher-layer parameter,ssb-SubcarrierOffset.
 8. The UE of claim 5, wherein based on the SS/PBCHblock being detected in the shared spectrum, the one LSB of the 1 kHzsubcarrier spacing-based offset information is used to identify SS/PBCHblock candidates in a quasi-co-location (QCL) relationship.